[ https://issues.apache.org/jira/browse/HBASE-6012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13294012#comment-13294012 ]
Hudson commented on HBASE-6012: ------------------------------- Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #51 (See [https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/51/]) HBASE-6012 Handling RegionOpeningState for bulk assign (Chunhui) (Revision 1349377) Result = FAILURE tedyu : Files : * /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/ServerManager.java * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/master/handler/ServerShutdownHandler.java * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/protobuf/ProtobufUtil.java * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/protobuf/ResponseConverter.java * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/HRegionServer.java * /hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/master/TestAssignmentManager.java > Handling RegionOpeningState for bulk assign > ------------------------------------------- > > Key: HBASE-6012 > URL: https://issues.apache.org/jira/browse/HBASE-6012 > Project: HBase > Issue Type: Bug > Affects Versions: 0.96.0 > Reporter: chunhui shen > Assignee: chunhui shen > Fix For: 0.96.0 > > Attachments: HBASE-6012.patch, HBASE-6012v2.patch, > HBASE-6012v3.patch, HBASE-6012v4.patch, HBASE-6012v5.patch, > HBASE-6012v6.patch, HBASE-6012v7.patch, HBASE-6012v8.patch > > > Since HBASE-5914, we using bulk assign for SSH > But in the bulk assign case if we get an ALREADY_OPENED case there is no one > to clear the znode created by bulk assign. > Another thing, when RS opening a list of regions, if one region is already in > transition, it will throw RegionAlreadyInTransitionException and stop opening > other regions. -- 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