You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Todd Lipcon (JIRA)" <ji...@apache.org> on 2011/08/30 04:46:38 UTC

[jira] [Updated] (HBASE-4287) If region opening fails, try to transition region back to "offline" in ZK

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

Todd Lipcon updated HBASE-4287:
-------------------------------

    Attachment: 0004-HBASE-4287.-FAILED_OPEN-state-in-ZK.patch

Here's a patch which I've tested and basically works on a cluster (well, an 0.90.x cluster).

I didn't follow the 4015 work closely, but I think this state makes sense.

> If region opening fails, try to transition region back to "offline" in ZK
> -------------------------------------------------------------------------
>
>                 Key: HBASE-4287
>                 URL: https://issues.apache.org/jira/browse/HBASE-4287
>             Project: HBase
>          Issue Type: Improvement
>          Components: master, regionserver
>    Affects Versions: 0.90.4
>            Reporter: Todd Lipcon
>            Assignee: Todd Lipcon
>             Fix For: 0.94.0
>
>         Attachments: 0004-HBASE-4287.-FAILED_OPEN-state-in-ZK.patch
>
>
> In the case that region-opening fails, we currently just close the region again, but don't do anything to the node in ZK. Instead, we should attempt to transition it from the OPENING state back to an OFFLINE state, or perhaps a new FAILED_OPEN state. Otherwise, we have to wait for the full timeoutMonitor period to elapse, which can be quite a long time.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira