hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Duo Zhang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-17372) Make AsyncTable thread safe
Date Sat, 31 Dec 2016 13:22:58 GMT

    [ https://issues.apache.org/jira/browse/HBASE-17372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15789509#comment-15789509
] 

Duo Zhang commented on HBASE-17372:
-----------------------------------

So maybe we could add the default rpc timeout config back? For exists, get and scan, we will
use the readRpcTimeout. For put and delete, we will use the writeRpcTimeout. Other operations
will just use the defaultRpcTimeout.

When adding the coprcoessor support for async table, I noticed that it is awkward to use either
readRpcTimeout or writeRpcTimeout as its rpcTimeout...

Let me find a way to do this.

> Make AsyncTable thread safe
> ---------------------------
>
>                 Key: HBASE-17372
>                 URL: https://issues.apache.org/jira/browse/HBASE-17372
>             Project: HBase
>          Issue Type: Sub-task
>          Components: asyncclient, Client
>    Affects Versions: 2.0.0
>            Reporter: Duo Zhang
>            Assignee: Duo Zhang
>             Fix For: 2.0.0
>
>         Attachments: HBASE-17372-v1.patch, HBASE-17372.patch
>
>
> The most methods are already thread safe. The problem is that we have some methods that
used to set timeout, we need to remove these methods and add a parameter for each call to
specific timeout settings.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message