[
https://issues.apache.org/jira/browse/HBASE-16664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15567473#comment-15567473
]
Phil Yang commented on HBASE-16664:
-----------------------------------
{quote}
My understanding is single-get is one operation and one call for api, but multi
get is multi operations although it is also just one call for api
{quote}
Now matter what a "operation" is. All api in Table need a total timeout,
because it is more easy to understand for users. We can split into two
operation timeout settings for single and batch, but I am not a fan for this.
As I said, I think supporting read/write rpc timeout is not a good idea. We can
use different instances for different timeout settings.
{quote}
2 and 3 maybe in different threads
{quote}
It may be a wrong usage? Table is not thread-safe, although for some methods if
we access them in different threads we may not fail, but we don't have to keep
this "feature", right?
> 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)
