impala-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matthew Jacobs (JIRA)" <>
Subject [jira] [Resolved] (IMPALA-5156) Drop VLOG level passed into Kudu client
Date Sun, 09 Apr 2017 18:44:41 GMT


Matthew Jacobs resolved IMPALA-5156.
       Resolution: Fixed
    Fix Version/s: Impala 2.9.0

commit 676a88f346c3dac57ffe0b5742a64ee7136b6bb1
Author: Matthew Jacobs <>
Date:   Tue Apr 4 13:36:01 2017 -0700

    IMPALA-5156: Drop VLOG level passed into Kudu client
    The Kudu logging is very verbose and all of the logging may
    affect performance. This change reduces the Kudu client log
    level to v-1, since Impala is typically run at v=1 and isn't
    too noisy.
    In some simple concurrency testing, Todd found that reducing
    the vlog level resulted in an increase in throughput from
    ~17 qps to 60qps.
    Change-Id: I6f160e20de37ac13887ccfebc5fb1d595fd05db1
    Reviewed-by: Matthew Jacobs <>
    Tested-by: Impala Public Jenkins

> Drop VLOG level passed into Kudu client
> ---------------------------------------
>                 Key: IMPALA-5156
>                 URL:
>             Project: IMPALA
>          Issue Type: Improvement
>          Components: Backend, Perf Investigation
>    Affects Versions: Impala 2.8.0
>            Reporter: Todd Lipcon
>             Fix For: Impala 2.9.0
> I'm running a concurrent stress workload with lots of small queries. By changing the
impalad vlog level from 1 to 0, my QPS went from ~17qps to around 60qps.
> We should consider passing FLAGS_v - 1 into Kudu's vlog level, since we generally assume
that VLOG=1 is allowed to be relatively noisy (eg logging thread start/stop, etc) whereas
it seems like Impala's policy is that VLOG(1) should be fairly quiet.

This message was sent by Atlassian JIRA

View raw message