You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Ted Yu (JIRA)" <ji...@apache.org> on 2016/11/18 18:33:58 UTC

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

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

Ted Yu commented on HBASE-17127:
--------------------------------

lgtm , pending QA run.

> 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
>            Reporter: Yu Li
>            Assignee: Yu Li
>         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 incorrect 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)