You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Andrew Purtell (JIRA)" <ji...@apache.org> on 2018/09/07 17:17:00 UTC

[jira] [Commented] (HBASE-20307) LoadTestTool prints too much zookeeper logging

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

Andrew Purtell commented on HBASE-20307:
----------------------------------------

We do reach in to log4j and set log level in other places, like various unit tests, and hardcode the log level to something that silences the log lines we want to avoid; however, this approach does not address either of the OPs suggestions:

bq. Hide it behind -verbose flag 

or 

bq. point people at log4j configuration but don't print it by default.

It seems pretty easy to wrap this
{code}
+    LogManager.getLogger(ZooKeeper.class.getName()).setLevel(Level.WARN);
{code}
with a conditional that checks if a verbose flag has been parsed on the command line, or not. Do that and I'd +1 this change.

> LoadTestTool prints too much zookeeper logging
> ----------------------------------------------
>
>                 Key: HBASE-20307
>                 URL: https://issues.apache.org/jira/browse/HBASE-20307
>             Project: HBase
>          Issue Type: Bug
>          Components: tooling
>            Reporter: Mike Drob
>            Assignee: Colin Garcia
>            Priority: Major
>              Labels: beginner
>         Attachments: HBASE-20307.000.patch
>
>
> When running ltt there is a ton of ZK related cruft that I probably don't care about. Hide it behind -verbose flag or point people at log4j configuration but don't print it by default.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)