[
https://issues.apache.org/jira/browse/HBASE-16664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15567335#comment-15567335
]
Duo Zhang commented on HBASE-16664:
-----------------------------------
Multi get also uses batch, and it will be executed with AsyncProcess, and I
think there is no 'uncertain operations' here right? And if user think he/she
does not need an operation timeout then just set it to Long.MAX_VALUE. But
ignore operation timeout will hurt the user who use multi get and multi put.
> 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, 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)
