hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-17127) Locate region should fail fast if underlying Connection already closed
Date Tue, 21 Mar 2017 01:14:42 GMT

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

Hudson commented on HBASE-17127:

SUCCESS: Integrated in Jenkins build HBase-1.3-JDK8 #138 (See [https://builds.apache.org/job/HBase-1.3-JDK8/138/])
HBASE-17175 backport HBASE-17127 (Locate region should fail fast if (liyu: rev 98b5d2cd4b0badef5f576cb35c8c8f1df1c88899)
* (edit) hbase-client/src/main/java/org/apache/hadoop/hbase/client/ConnectionManager.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

View raw message