You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2010/09/18 23:58:33 UTC

[jira] Updated: (HBASE-3016) Refactor zk logging in trunk; do less and and identifier to log messages to help debugging

     [ https://issues.apache.org/jira/browse/HBASE-3016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

stack updated HBASE-3016:
-------------------------

    Attachment: 3016.txt

Here is what I committed.

> 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
>            Assignee: stack
>             Fix For: 0.90.0
>
>         Attachments: 3016.txt
>
>
> 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.