[
https://issues.apache.org/jira/browse/HBASE-16664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15567813#comment-15567813
]
Phil Yang commented on HBASE-16664:
-----------------------------------
I think the start time should be the TS that user calls the API? Queuing time
should also be considered as part of operation time, this is one of reasons why
rpctimeout+retriesTimes are not enough.
For other operations using AP, for example, delete, we also need call start
before enqueuing?
> 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)
