[ https://issues.apache.org/jira/browse/HBASE-6046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13283976#comment-13283976 ]
ramkrishna.s.vasudevan commented on HBASE-6046: ----------------------------------------------- I think its better to do finishInitialization step fully. Ashutosh and myself saw problems in the current way of handlng -> MAster not knowing that a RS has gone down. -> So no split happens -> So we need to do all the steps in finish initialization. -> We tried to do all the steps from waitForRegionServers till the end, but here again the masterfilesystem is initializing the splitlogmanager. So can we call finish initialization itself once again? > Master retry on ZK session expiry causes inconsistent region assignments. > ------------------------------------------------------------------------- > > Key: HBASE-6046 > URL: https://issues.apache.org/jira/browse/HBASE-6046 > Project: HBase > Issue Type: Bug > Components: master > Affects Versions: 0.92.1, 0.94.0 > Reporter: Gopinathan A > Assignee: ramkrishna.s.vasudevan > Fix For: 0.92.2, 0.94.1 > > > 1> ZK Session timeout in the hmaster leads to bulk assignment though all the > RSs are online. > 2> While doing bulk assignment, if the master again goes down & restart(or > backup comes up) all the node created in the ZK will now be tried to reassign > to the new RSs. This is leading to double assignment. > we had 2800 regions, among this 1900 region got double assignment, taking the > region count to 4700. -- 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