[
https://issues.apache.org/jira/browse/HBASE-4245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13093068#comment-13093068
]
stack commented on HBASE-4245:
------------------------------
@Ram Do you think you reproduced Todds' scenario faithfully? The code could be
different in TRUNK such that we do recover but I don't see in your steps the
successful open of .META. followed by a crash of the server hosting .META. such
that the ServerShutdownHandler has to deal with case of root and meta being
offline at same time.
> Cluster hangs if RS serving root fails during startup sequence
> --------------------------------------------------------------
>
> Key: HBASE-4245
> URL: https://issues.apache.org/jira/browse/HBASE-4245
> Project: HBase
> Issue Type: Bug
> Components: master
> Affects Versions: 0.90.3
> Reporter: Todd Lipcon
> Assignee: ramkrishna.s.vasudevan
>
> On a large-ish cluster, the following sequence of events was seen to happen:
> - master started, ROOT and META were both unassigned
> - ROOT is assigned to rs01
> - META is assigned to rs02
> - Upon open of META, it writes its location into ROOT on rs01
> - rs01 crashes while appending to its HLog due to some other bug
> - rs02 fails the region open sequence
> - master notices that rs01 has crashed, and enqueues a ServerShutdownHandler
> - ServerShutdownHandler blocks on CatalogTracker.waitForMeta() since ROOT and
> META are not assigned yet
> - master times out assignment of META, but never succeeds because ROOT
> location is still marked as rs01
> This causes the cluster to never start up.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
