[ https://issues.apache.org/jira/browse/HBASE-6281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13404584#comment-13404584 ]
Hadoop QA commented on HBASE-6281: ---------------------------------- -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12534117/HBASE-6281_94_2.patch against trunk revision . +1 @author. The patch does not contain any @author tags. +1 tests included. The patch appears to include 3 new or modified tests. -1 patch. The patch command could not apply the patch. Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/2304//console This message is automatically generated. > Assignment need not be called for disabling table regions during clean > cluster start up. > ---------------------------------------------------------------------------------------- > > Key: HBASE-6281 > URL: https://issues.apache.org/jira/browse/HBASE-6281 > Project: HBase > Issue Type: Bug > Affects Versions: 0.92.1, 0.94.0 > Reporter: rajeshbabu > Assignee: rajeshbabu > Fix For: 0.92.2, 0.96.0, 0.94.1 > > Attachments: 6281-trunk-v2.txt, HBASE-6281_94.patch, > HBASE-6281_94_2.patch, HBASE-6281_trunk.patch > > > Currently during clean cluster start up if there are tables in DISABLING > state, we do bulk assignment through assignAllUserRegions() and after region > is OPENED in RS, master checks if the table is in DISBALING/DISABLED state > (in Am.regionOnline) and again calls unassign. This roundtrip can be avoided > even before calling assignment. > This JIRA is to address the above scenario. -- 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