[
https://issues.apache.org/jira/browse/HBASE-16664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15567778#comment-15567778
]
Heng Chen commented on HBASE-16664:
-----------------------------------
it should be better for tracker.start() moved into
CancellableRegionServerCallable.call as original due to the request maybe
queued in threadPool? The time will be more accurate. As race condition for
tracker.start(), just make the globalStartTime to be volatile is OK?
> 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: 1.patch, HBASE-16664-branch-1-v1.patch,
> HBASE-16664-branch-1-v1.patch, HBASE-16664-branch-1.1-v1.patch,
> HBASE-16664-branch-1.2-v1.patch, HBASE-16664-branch-1.3-v1.patch,
> HBASE-16664-v1.patch, HBASE-16664-v2.patch, HBASE-16664-v3.patch,
> HBASE-16664-v4.patch, HBASE-16664-v5.patch, HBASE-16664-v6.patch,
> testhcm.patch
>
>
> Rpc/operation timeout logic in AsyncProcess is broken. And Table's
> set*Timeout does not take effect in its AP or BufferedMutator.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
