You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2011/03/15 02:19:29 UTC

[jira] Resolved: (HBASE-3637) Region stuck in OPENED state

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

stack resolved HBASE-3637.
--------------------------

    Resolution: Won't Fix

Will fix HBASE-3638 instead

> Region stuck in OPENED state
> ----------------------------
>
>                 Key: HBASE-3637
>                 URL: https://issues.apache.org/jira/browse/HBASE-3637
>             Project: HBase
>          Issue Type: Bug
>          Components: master
>    Affects Versions: 0.92.0
>            Reporter: Todd Lipcon
>            Priority: Critical
>             Fix For: 0.92.0
>
>
> I don't 100% understand how this happened, but the following was observed:
> - META is in OPENED state in ZK, for a server which no longer exists
> - Handler sees that server is dead, and figures that the RIT timeout will handle it
> - RIT timeout sees that it's already in OPENED state, and assumes that the OPENED handler will handle it
> - loops in timeout state forever, never actually getting reassigned

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