Refactor zk logging in trunk; do less and and identifier to log messages to
help debugging
------------------------------------------------------------------------------------------
Key: HBASE-3016
URL: https://issues.apache.org/jira/browse/HBASE-3016
Project: HBase
Issue Type: Improvement
Components: zookeeper
Reporter: stack
Fix For: 0.90.0
Currently all logging is done by zookeeperwatcher so can add a zkw identifier
on the front of the log message. This happens for logging done by other
classes -- zkutil, zkconfig -- which makes it so can't turn off logging using
log4j config (its all or nothing).
Also, zk gives connections a sessionid. To tie zk logs to hbase logs, we
should include sessionid in the zkw identifier. It helps debugging especially
when using minihbasecluster where clients, master, rs, and zk server are all
logging to the same file.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.