You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues-all@impala.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2021/03/25 01:05:00 UTC

[jira] [Commented] (IMPALA-10604) Allow setting KuduClient's verbose logging level directly

    [ https://issues.apache.org/jira/browse/IMPALA-10604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17308269#comment-17308269 ] 

ASF subversion and git services commented on IMPALA-10604:
----------------------------------------------------------

Commit 452c2f1f7f9cc4c8472ab38949e9990281dcc3a3 in impala's branch refs/heads/master from Thomas Tauber-Marshall
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=452c2f1 ]

IMPALA-10604: Allow setting KuduClient's verbose log level directly

This patch adds a flag --kudu_client_v which allows setting the
verbose logging level for the KuduClient to a value other than the
level for the rest of Impala (set by -v) in order to enable debugging
of issues in the KuduClient without producing the enormous amount of
logging that comes with setting a high -v value on all of Impala.

Testing:
- Manually set --kudu_client_v and confirmed that the expected logging
  is produced.

Change-Id: Ib39358709ee714b8cdffd72a0ee58f66d5fab37e
Reviewed-on: http://gerrit.cloudera.org:8080/17222
Reviewed-by: Impala Public Jenkins <im...@cloudera.com>
Tested-by: Impala Public Jenkins <im...@cloudera.com>


> Allow setting KuduClient's verbose logging level directly
> ---------------------------------------------------------
>
>                 Key: IMPALA-10604
>                 URL: https://issues.apache.org/jira/browse/IMPALA-10604
>             Project: IMPALA
>          Issue Type: Improvement
>    Affects Versions: Impala 4.0
>            Reporter: Thomas Tauber-Marshall
>            Assignee: Thomas Tauber-Marshall
>            Priority: Major
>
> Currently, Impala sets KuduClient's verbose logging level to the same as its own level (taken from the -v flag) minus 1. Since KuduClient doesn't have any way of setting vmodule, this means that to get verbose logging inside KuduClient users must turn it on to a high level for all of Impala, which can produce an enormous volume of logging. making it hard to collect, share, and analyze logs.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org