[jira] [Commented] (HBASE-17127) Locate region should fail fast if underlying Connection already closed

["Hudson (JIRA)" <ji...@apache.org>]

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

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

FAILURE: Integrated in Jenkins build HBase-0.98-on-Hadoop-1.1 #1293 (See [https://builds.apache.org/job/HBase-0.98-on-Hadoop-1.1/1293/])
HBASE-17127 Locate region should fail fast if underlying Connection (apurtell: rev 6ea27ebed59c7ded4135330114c35469a3bab99a)
* (edit) hbase-client/src/main/java/org/apache/hadoop/hbase/client/HConnectionManager.java
* (edit) hbase-client/src/test/java/org/apache/hadoop/hbase/client/TestClientNoCluster.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.4#6332)