[ https://issues.apache.org/jira/browse/HBASE-10333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13875406#comment-13875406 ]
Hudson commented on HBASE-10333: -------------------------------- SUCCESS: Integrated in HBase-TRUNK-on-Hadoop-1.1 #56 (See [https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-1.1/56/]) HBASE-10333 Assignments are not retained on a cluster start (jxiang: rev 1558963) * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/master/AssignmentManager.java * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/master/HMaster.java > 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 > Affects Versions: 0.98.0, 0.96.1.1 > Reporter: Devaraj Das > Assignee: Jimmy Xiang > Fix For: 0.98.0, 0.96.2, 0.99.0 > > Attachments: hbase-10333.patch > > > 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)