[
https://issues.apache.org/jira/browse/HBASE-10333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13871263#comment-13871263
]
Devaraj Das commented on HBASE-10333:
-------------------------------------
This issue is there in 0.96.1+
I think the issue is guaranteed to happen in those cluster-restart cases where
the node hosting the meta previously is not there in the restarted cluster, or
the regionserver process comes up on a different port on the same node after
the restart.
> Assignments are not retained on a cluster start
> -----------------------------------------------
>
> Key: HBASE-10333
> URL: https://issues.apache.org/jira/browse/HBASE-10333
> Project: HBase
> Issue Type: Bug
> Reporter: Devaraj Das
> Assignee: Jimmy Xiang
>
> When a cluster is fully shutdown and then started up again with
> hbase.master.startup.retainassign set to true, I noticed that the assignments
> are not retained. Upon digging, it seems like HBASE-10101 made a change due
> to which the server holding the META previously is added to dead-servers (in
> _HMaster.assignMeta_). Later on, this makes the AssignmentManager think that
> the master recovered from a failure as opposed to a fresh cluster start (the
> ServerManager.deadServers list is not empty in the check within
> _AssignmentManager.processDeadServersAndRegionsInTransition_)
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
