Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Mon, 17 Dec 2012 19:12:17 +0000 (UTC)
From: "stack (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12623311.1355187842559.18022.1355771537031@arcas>
In-Reply-To: <JIRA.12623311.1355187842559@arcas>
References: <JIRA.12623311.1355187842559@arcas>
Subject: [jira] [Commented] (HBASE-7318) Add verbose logging option to
 HConnectionManager
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HBASE-7318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13534176#comment-13534176 ] 

stack commented on HBASE-7318:
------------------------------

Patch looks good Sergey.  Do you have to introduce the new flag?  Could you not log the new stuff at TRACE level?  Would that work for you?  Then the config. will be in the place folks expect to find it in, in log4j.properties?
                
> Add verbose logging option to HConnectionManager
> ------------------------------------------------
>
>                 Key: HBASE-7318
>                 URL: https://issues.apache.org/jira/browse/HBASE-7318
>             Project: HBase
>          Issue Type: Improvement
>    Affects Versions: 0.96.0
>            Reporter: Sergey Shelukhin
>            Assignee: Sergey Shelukhin
>            Priority: Minor
>             Fix For: 0.96.0
>
>         Attachments: HBASE-7318-v0.patch
>
>
> In the course of HBASE-7250 I found that client-side errors (as well as server-side errors, but that's another question) are hard to debug.
> I have some local commits with useful, not-that-hacky HConnectionManager logging added.
> Need to "productionize" it to be off by default but easy-to-enable for debugging.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira