[
https://issues.apache.org/jira/browse/HBASE-16664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15520289#comment-15520289
]
Heng Chen commented on HBASE-16664:
-----------------------------------
{quote}
The tracker must be started from beginning, not each call.
{quote}
There is no difference start from begining and do it each call, the logic has
been controlled in tracker.start inside.
{quote}
And in fact we will create new CancellableRegionServerCallable in each
retrying, so the operation timeout is broken.
{quote}
NO, callable is created outside of AP for delete, mutate. Only batch callable
will be created each thread.
{quote}
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.
{quote}
It seems you just need to control remaining time for each call with remaining
operation time and rpcTimeOut
> 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
> Assignee: Phil Yang
> Attachments: HBASE-16664-v1.patch, 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)
