Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Mon, 20 Mar 2017 22:24:41 +0000 (UTC)
From: "Hudson (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.13021804.1479491952000.72419.1490048681813@Atlassian.JIRA>
In-Reply-To: <JIRA.13021804.1479491952000@Atlassian.JIRA>
References: <JIRA.13021804.1479491952000@Atlassian.JIRA> <JIRA.13021804.1479491952661@jira-lw-us.apache.org>
Subject: [jira] [Commented] (HBASE-17127) Locate region should fail fast if
 underlying Connection already closed
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Mon, 20 Mar 2017 22:24:48 -0000


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

Hudson commented on HBASE-17127:
--------------------------------

SUCCESS: Integrated in Jenkins build HBase-1.3-IT #10 (See [https://builds.apache.org/job/HBase-1.3-IT/10/])
HBASE-17175 backport HBASE-17127 (Locate region should fail fast if (liyu: rev 98b5d2cd4b0badef5f576cb35c8c8f1df1c88899)
* (edit) hbase-client/src/test/java/org/apache/hadoop/hbase/client/TestClientNoCluster.java
* (edit) hbase-client/src/main/java/org/apache/hadoop/hbase/client/ConnectionManager.java


> Locate region should fail fast if underlying Connection already closed
> ----------------------------------------------------------------------
>
>                 Key: HBASE-17127
>                 URL: https://issues.apache.org/jira/browse/HBASE-17127
>             Project: HBase
>          Issue Type: Bug
>    Affects Versions: 1.1.7, 1.2.4
>            Reporter: Yu Li
>            Assignee: Yu Li
>             Fix For: 2.0.0, 1.4.0, 1.2.5, 0.98.24, 1.1.8
>
>         Attachments: HBASE-17127.patch
>
>
> Currently if try to locate region when underlying connection is closed, we will retry and wait at least 10s for each round until exhausted (refer to the catch clause of {{RpcRetryingCallerImpl#callWithRetries}} and {{RegionServerCallable#sleep}} for more details), which is unnecessary and time-costing.
> The issue is caused by user incorrectly manipulating connection, which shows the disadvantage of force user to handle connection life cycle and proves the necessity to support auto-managed connection as we did before, as indicated in HBASE-17009
> In this JIRA we will make it fail fast in the above case.


--
This message was sent by Atlassian JIRA
(v6.3.15#6346)