-
Notifications
You must be signed in to change notification settings - Fork 594
Reduce verbosity of zookeeper logging #1547
Reduce verbosity of zookeeper logging #1547
Conversation
I'm inclined to set all of
And there's also httpUrlConnection which is really noisy:
Alternatively we could just set Comments welcome. |
I'm OK with logging everything when in verbose, but we should specify what should not be omitted when logger is not in verbose mode. For ZK, I'd like to see some important information gets printed. For example, the ZK hostport that gets connected to. +1 for not logging P.S.: I was fixing Python logging months ago and realized that carefully assigning proper logging level to every log is not an easy job. And that If you think some levels are fine, not everyone will agree... ("Why I have to add |
My main motivation is to reduce the verbosity of the zookeeper logs - when in verbose mode or not - since zookeeper is so log intensive with basic info that I is never used. Setting ZK to WARN is not uncommon. Having INFO appear, even in verbose mode, makes reading the logs harder IMO, especially when reading CI logs. For example, these log lines get generated repeatedly:
@objmagic do you have examples of the ZK log lines that you'd like to still see? Also note that we access ZK through Curator which also logs heavily so we will still have plenty of output for each ZK interaction. |
ok make sense. 👍 for setting ZK to warning. |
Understood now. Agree 👍
|
@objmagic I removed Once we've fully abandoned that pattern in favor of throwing meaningful exceptions, then I think we can remove more |
Removed verbosity on kill as well as noisy pex logging that was necessary when we first introduced the pex build and needed to troubleshoot frequently, which is no longer the case. We can uncomment if we need move debug info. This is what we won't see lots of anymore:
|
Yes those logs should be removed. |
* reduce more log verbosity
ZK logging is notoriously verbose so turning that down. The submit output is soooo much more bearable now...