Patrick Hunt commented on ZOOKEEPER-912:

Hi John, thanks for the feedback

bq. I've actually had to repackage the zk jar without log4j.xml to tone down 
the logging.

well we don't have a log4j.xml at all, we do have a log4j.properties but that's 
not included in our primary or "maven bin" jar files. I just looked again and I 
don't see it included (at least in 3.3.1) Perhaps this is being pulled in from 
elsewhere in your environment?

We do provide a default log4j.properties in the conf directory of the release 
artifact. However the intent is for users to either use that directly or 
customize it based on their needs, which is why it's a config file and not 

bq. If I could weigh in on this one too... <logging levels>

That's basically what we do. I grant that we skew to pushing more detail at 
INFO that might be DEBUG, and some DEBUG that should be TRACE. We have been 
working on that of late (see JIRA, a number of logging level changes went into 
3.3). We could push a few more of the info messages to debug, but I'm reticent 
for a few reasons. Primarily the fact that we often get reports from users who 
see issues where the only detail we have to go on (esp given this is a complex 
distributed system) is the info (and higher) level logs. My experience 
supporting a number of production teams (15+) tells me this would compromise 
our ability to help them resolve issues.

> 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.

Reply via email to