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

Phil Yang commented on HBASE-16664:
-----------------------------------

I think maybe all branche-1.x have the bug. The difference of master and 
branch-1 is we use AP in Delete, too. So in branch-1 it only affect Put.
We have a timeout when we construct AsyncProcess. But we pass rpcTimeout.(See 
ConnectionImplementation L1833) which is split read/write two timeout now. The 
correct timeout should be writeRpcTimeout because in AP we only do write 
operations?
In table we have setOperationTimeout and setRpcTimeout, we can set the new 
value which is different from Configuration. But they don't change timeout in 
AP. And AP is complicated so I have not found where is the logic of operation 
timeout.. I'm not sure if we have.


> Timeout logic in AsyncProcess is broken
> ---------------------------------------
>
>                 Key: HBASE-16664
>                 URL: https://issues.apache.org/jira/browse/HBASE-16664
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Phil Yang
>         Attachments: testhcm.patch
>
>
> Have not checked the root cause, but I think timeout of all operations in 
> AsyncProcess is broken



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to