hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yu Li (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-17127) Locate region should fail fast if underlying Connection already closed
Date Sat, 19 Nov 2016 16:37:58 GMT

     [ https://issues.apache.org/jira/browse/HBASE-17127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Yu Li updated HBASE-17127:
    Affects Version/s: 1.1.7
         Hadoop Flags: Reviewed
        Fix Version/s: 1.1.8

Thanks [~tedyu] and [~stack] for review.

Pushed into branch-1/1.1/1.2 and master branch. [~mantonov] please let me know whether you'd
like this one into 1.3.0 or leave it for 1.3.1, thanks.

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