[ https://issues.apache.org/jira/browse/ZOOKEEPER-912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12925719#action_12925719 ]
Patrick Hunt commented on ZOOKEEPER-912: ---------------------------------------- bq. Zookeeper logs nearly everything at least at level "info," regardless of severity. that's incorrect. I did a quick grep for logging in the main src and see the following: egrep -R "LOG\.error" src/java/main/. |wc -l 78 egrep -R "LOG\.warn" src/java/main/. |wc -l 175 egrep -R "LOG\.info" src/java/main/. |wc -l 127 egrep -R "LOG\.debug" src/java/main/. |wc -l 114 egrep -R "LOG\.trace" src/java/main/. |wc -l 28 So actually we log mostly at WARN severity. Perhaps you think this because you mainly see INFO messages, but that's to be expected (typically things work, we only log WARN/ERROR when bad things happen). I didn't say anything about all/nothing. Check the code, we have a number of messages at various levels, incl trace/debug. If you don't want to see the informational messages for a particular class you can configure that. As I pointed out earlier: http://hadoop.apache.org/zookeeper/docs/current/zookeeperInternals.html#sc_logging We consider both the messages you listed to be informational given that we expect/recover from the second. > 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.