Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Fri, 23 Sep 2016 03:28:22 +0000 (UTC)
From: "Duo Zhang (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12974125.1464675867000.645139.1474601302185@Atlassian.JIRA>
In-Reply-To: <JIRA.12974125.1464675867000@Atlassian.JIRA>
References: <JIRA.12974125.1464675867000@Atlassian.JIRA> <JIRA.12974125.1464675867359@arcas>
Subject: [jira] [Commented] (HBASE-15921) Add first AsyncTable impl and
 create TableImpl based on it
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Fri, 23 Sep 2016 03:28:24 -0000


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

Duo Zhang commented on HBASE-15921:
-----------------------------------

Let's talk about the retry and timeout logic.

In general, I think we should only do retry at one place, which means, we always restart from the beginning. We can config different timeout values for different stages, but the actual timeout when executing the operation will also be limited by the whole operation timeout config. This could simplify our logic. For example, we do not need to implement retry logic in rpc(Yeah I have just removed the reconnect logic in NettyRpcConnection). And it is also much easier for us to implement the backoff logic.

What do you think? [~stack] [~carp84] [~chenheng].

Thanks.

> Add first AsyncTable impl and create TableImpl based on it
> ----------------------------------------------------------
>
>                 Key: HBASE-15921
>                 URL: https://issues.apache.org/jira/browse/HBASE-15921
>             Project: HBase
>          Issue Type: Improvement
>    Affects Versions: 2.0.0
>            Reporter: Jurriaan Mous
>            Assignee: Duo Zhang
>             Fix For: 2.0.0
>
>         Attachments: HBASE-15921-v2.patch, HBASE-15921.demo.patch, HBASE-15921.patch, HBASE-15921.v1.patch
>
>
> First we create an AsyncTable interface with implementation without the Scan functionality. Those will land in a separate patch since they need a refactor of existing scans.
> Also added is a new TableImpl to replace HTable. It uses the AsyncTableImpl internally and should be a bit faster because it does jump through less hoops to do ProtoBuf transportation. This way we can run all existing tests on the AsyncTableImpl to guarantee its quality.


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