hadoop-zookeeper-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John L. Singleton (JIRA)" <j...@apache.org>
Subject [jira] Commented: (ZOOKEEPER-912) ZooKeeper client logs trace and debug messages at level INFO
Date Thu, 04 Nov 2010 20:33:03 GMT

    [ https://issues.apache.org/jira/browse/ZOOKEEPER-912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12928335#action_12928335

John L. Singleton commented on ZOOKEEPER-912:

Hi Patrick and Anthony,

If I may comment on this issue, I have recently had problems with Zookeeper and the verbosity
of it's default logging. My problem is that a) the default logging is really too verbose in
general and that b) including Zookeeper in your classpath causes Zookeeper's log4j.xml file
to override established logging. To get around this I've actually had to repackage the zk
jar without log4j.xml to tone down the logging.

Now, as for the issue above, I agree that most of those messages, if they are used for "debugging"
they really need to be at the DEBUG level, not INFO. 

Love ZK! Keep up the good work!


> ZooKeeper client logs trace and debug messages at level INFO
> ------------------------------------------------------------
>                 Key: ZOOKEEPER-912
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-912
>             Project: Zookeeper
>          Issue Type: Improvement
>          Components: java client
>    Affects Versions: 3.3.1
>            Reporter: Anthony Urso
>            Assignee: Anthony Urso
>            Priority: Minor
>             Fix For: 3.4.0
>         Attachments: zk-loglevel.patch
> ZK logs a lot of uninformative trace and debug messages to level INFO.  This fuzzes up
everything and makes it easy to miss useful log info. 

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message