[ https://issues.apache.org/jira/browse/HBASE-5916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13284517#comment-13284517 ]
Hudson commented on HBASE-5916: ------------------------------- Integrated in HBase-0.94 #222 (See [https://builds.apache.org/job/HBase-0.94/222/]) HBASE-5916 RS restart just before master intialization we make the cluster non operative(RajeshBabu) (Revision 1343326) Result = FAILURE ramkrishna : Files : * /hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/master/AssignmentManager.java * /hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/master/HMaster.java * /hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/master/MasterFileSystem.java * /hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/master/ServerManager.java * /hbase/branches/0.94/src/test/java/org/apache/hadoop/hbase/regionserver/TestRSKilledWhenMasterInitializing.java > RS restart just before master intialization we make the cluster non operative > ----------------------------------------------------------------------------- > > Key: HBASE-5916 > URL: https://issues.apache.org/jira/browse/HBASE-5916 > Project: HBase > Issue Type: Bug > Affects Versions: 0.92.1, 0.94.0 > Reporter: ramkrishna.s.vasudevan > Assignee: ramkrishna.s.vasudevan > Priority: Critical > Fix For: 0.96.0, 0.94.1 > > Attachments: HBASE-5916_94.patch, HBASE-5916_trunk.patch, > HBASE-5916_trunk_1.patch, HBASE-5916_trunk_1.patch, HBASE-5916_trunk_2.patch, > HBASE-5916_trunk_3.patch, HBASE-5916_trunk_4.patch, > HBASE-5916_trunk_v5.patch, HBASE-5916_trunk_v6.patch, > HBASE-5916_trunk_v7.patch, HBASE-5916_trunk_v8.patch, > HBASE-5916_trunk_v9.patch, HBASE-5916v8.patch > > > Consider a case where my master is getting restarted. RS that was alive when > the master restart started, gets restarted before the master initializes the > ServerShutDownHandler. > {code} > serverShutdownHandlerEnabled = true; > {code} > In this case when the RS tries to register with the master, the master will > try to expire the server but the server cannot be expired as still the > serverShutdownHandler is not enabled. > This case may happen when i have only one RS gets restarted or all the RS > gets restarted at the same time.(before assignRootandMeta). > {code} > LOG.info(message); > if (existingServer.getStartcode() < serverName.getStartcode()) { > LOG.info("Triggering server recovery; existingServer " + > existingServer + " looks stale, new server:" + serverName); > expireServer(existingServer); > } > {code} > If another RS is brought up then the cluster comes back to normalcy. > May be a very corner case. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira