[
https://issues.apache.org/jira/browse/HBASE-3637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13006619#comment-13006619
]
Todd Lipcon commented on HBASE-3637:
------------------------------------
Some more context: this was from a test that was looping the following:
- install HBase
- wipe /hbase on HDFS
- start hbase, run smoke test, kill all servers
Notably, it wasn't clearing ZK between runs. So some leftover RIT data from a
previous HBase incarnation may be confusing this one's master.
> 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
