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 Tue, 03 Jan 2017 18:50:58 GMT

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

stack commented on HBASE-17372:

Thanks [~carp84]. Yes. We need a writeup.  I can do it in a new issue.

The split of rpc timeout came in with the below. It is in 2.0 and 1.4.

commit 30d7eeaefe431bc263519064662e6dc8ad8ff05a
Author: Vivek <vkoppuru@salesforce.com>
Date:   Fri Aug 5 17:25:06 2016 -0700

    HBASE-15866 Split hbase.rpc.timeout into *.read.timeout and *.write.timeout

    Signed-off-by: Andrew Purtell <apurtell@apache.org>
    Amending-Author: Andrew Purtell <apurtell@apache.org>

I'd mix that in. 

Would have a writeup for pre-1.4 and after.

> 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,
> 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

View raw message