You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Ted Yu (JIRA)" <ji...@apache.org> on 2013/01/09 04:54:13 UTC

[jira] [Comment Edited] (HBASE-7318) Add verbose logging option to HConnectionManager

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

Ted Yu edited comment on HBASE-7318 at 1/9/13 3:53 AM:
-------------------------------------------------------

Patch v2 fixes a compilation error:

[ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.5.1:compile (default-compile) on project hbase-server: Compilation failure
[ERROR] /Users/tyu/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/client/HConnectionManager.java:[2102,41] cannot find symbol
[ERROR] symbol  : method getExhaustiveDescription()
[ERROR] location: class org.apache.hadoop.hbase.client.RetriesExhaustedWithDetailsException
                
      was (Author: yuzhihong@gmail.com):
    Patch v2 fixes a compilation error.
                  
> 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: 7318-v2.patch, HBASE-7318-v0.patch, HBASE-7318-v1.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