[
https://issues.apache.org/jira/browse/HBASE-4193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13083982#comment-13083982
]
Hudson commented on HBASE-4193:
-------------------------------
Integrated in HBase-TRUNK #2111 (See
[https://builds.apache.org/job/HBase-TRUNK/2111/])
HBASE-4193 Enhance RPC debug logging with details on call contents
garyh :
Files :
* /hbase/trunk/conf/log4j.properties
* /hbase/trunk/src/main/java/org/apache/hadoop/hbase/ipc/HBaseServer.java
* /hbase/trunk/CHANGES.txt
* /hbase/trunk/src/main/java/org/apache/hadoop/hbase/ipc/WritableRpcEngine.java
* /hbase/trunk/src/main/java/org/apache/hadoop/hbase/util/Objects.java
> Enhance RPC debug logging to provide more details on call contents
> ------------------------------------------------------------------
>
> Key: HBASE-4193
> URL: https://issues.apache.org/jira/browse/HBASE-4193
> Project: HBase
> Issue Type: Improvement
> Components: ipc
> Reporter: Gary Helmling
> Assignee: Gary Helmling
> Priority: Minor
> Fix For: 0.92.0
>
> Attachments: HBASE-4193.patch, HBASE-4193_final.patch
>
>
> The current HBaseServer debug logging, while verbose, doesn't provide much
> information on the actual contents of RPC calls being handled. This makes it
> difficult to diagnose why some calls make take much longer to process that
> others. Have more information on the size of client calls, and the contents
> of those calls (especially in the case of batch or multi operations) would
> provide a lot more context for tracking down issues.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
