hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lars Hofhansl (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-6326) Avoid nested retry loops in HConnectionManager
Date Thu, 05 Jul 2012 17:34:36 GMT

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

Lars Hofhansl updated HBASE-6326:

    Status: Patch Available  (was: Open)
> Avoid nested retry loops in HConnectionManager
> ----------------------------------------------
>                 Key: HBASE-6326
>                 URL: https://issues.apache.org/jira/browse/HBASE-6326
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Lars Hofhansl
>            Assignee: Lars Hofhansl
>            Priority: Critical
>             Fix For: 0.96.0, 0.94.1
>         Attachments: 6326-trunk.txt, 6326.txt
> While testing client timeouts when the HBase is not available we found that even with
aggressive settings, it takes the client 10 minutes or more to finally receive an exception.
> Part of this is due to nested nested retry loops in locateRegion.
> locateRegion will first try to locate the table in meta (which is retried), then it will
try to locate the meta table is root (which is also retried).
> So for each retry of the meta lookup we retry the root lookup as well.
> I have have that avoids locateRegion retrying if it is called from code that already
has a retry loop.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message