hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-17007) Move ZooKeeper logging to its own log file
Date Thu, 03 Nov 2016 04:48:58 GMT

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

stack commented on HBASE-17007:

[~enis] A few of us were sitting around trying to tidy up logs.

ZK spews all over our log. It duplicates stuff we emit like the CLASSPATH and JVM properties
and then usually dumps a few Connection exceptions in our log just for good measure though
the cluster startup is 'clean' (unsettling any newbie operator for sure). It dumps all info
at LOG.info level so we can't even turn it down. Mighty [~esteban] had the good idea of having
the zk emissions in their own file. The separated log can still be correlated w/ events in
the hbase log given they timestamp the same on the rare occasion we need to match the two
(we have our own logging around lost session again making the zk back and forth around this
event redundant).

Rare if at all does the zk log have anything of import in it. Mostly it is just noise obscuring
the good stuff w/ its three or four lines every tens seconds heartbeating the ensemble.

This is what we were thinking today at least.

> Move ZooKeeper logging to its own log file
> ------------------------------------------
>                 Key: HBASE-17007
>                 URL: https://issues.apache.org/jira/browse/HBASE-17007
>             Project: HBase
>          Issue Type: Bug
>          Components: Zookeeper
>            Reporter: Esteban Gutierrez
>            Assignee: Esteban Gutierrez
>            Priority: Trivial
>         Attachments: 0001-HBASE-17007-Move-ZooKeeper-logging-to-its-own-log-fi.patch
> ZooKeeper logging can be too verbose. Lets move ZooKeeper logging to a different log

This message was sent by Atlassian JIRA

View raw message