hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-17372) Make AsyncTable thread safe
Date Wed, 04 Jan 2017 03:03:58 GMT

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

stack commented on HBASE-17372:
-------------------------------

On the setting of rpc timeout table wide, the hard thing to reason about is what happens if
you set the timeout while operations are ongoing. Perhaps if timeout were passed on construction
only? Yeah, being able to specify operationconfig per method invocation doubles up our API
which is kinda ugly/lazy. It is clear what is going on though and you can do settings per
call type -- our calls are different enough as you go across Get/Scan/Batch. Would be interested
in alternative proposal though.

> 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-v2.patch, HBASE-17372-v3.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