[
https://issues.apache.org/jira/browse/HBASE-16664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15515576#comment-15515576
]
Phil Yang commented on HBASE-16664:
-----------------------------------
The current CancellableRegionServerCallable's logic is wrong, I think. The
tracker must be started from beginning, not each call. And in fact we will
create new CancellableRegionServerCallable in each retrying, so the operation
timeout is broken.
My idea is pass a deadline (currentTime+operationTimeout) when we submit, we
just check the remaining time and get min of remaining and rpcTimeout for each
call.
And we have RpcRetryingCaller, but in AP we only use callWithoutRetries. If we
want to unify all operations into AP, the RpcRetryingCaller can be removed?
> 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)
