[
https://issues.apache.org/jira/browse/HBASE-9461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13766052#comment-13766052
]
Hadoop QA commented on HBASE-9461:
----------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12602913/ipc2.ucls
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/7201//console
This message is automatically generated.
> Some doc and cleanup in RPCServer
> ---------------------------------
>
> Key: HBASE-9461
> URL: https://issues.apache.org/jira/browse/HBASE-9461
> Project: HBase
> Issue Type: Bug
> Reporter: stack
> Assignee: stack
> Attachments: 9461.txt, ipc2.ucls
>
>
> RPC is a dog to follow. I want to do buffer pooling for reading requests but
> its tough drawing the diagram of who is doing what when. HBASE-8884 seems to
> have made it more involved still. This issue is about doing a bit of
> untangling.
--
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
