[
https://issues.apache.org/jira/browse/HBASE-6537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13437639#comment-13437639
]
Hadoop QA commented on HBASE-6537:
----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12540261/HBASE-6537-94-v2.patch
against trunk revision .
+1 @author. The patch does not contain any @author tags.
-1 tests included. The patch doesn't appear to include any new or modified
tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
-1 patch. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/2624//console
This message is automatically generated.
> Balancer compete with disable table will lead to cluster inconsistent
> ----------------------------------------------------------------------
>
> Key: HBASE-6537
> URL: https://issues.apache.org/jira/browse/HBASE-6537
> Project: HBase
> Issue Type: Bug
> Components: master
> Affects Versions: 0.94.0
> Reporter: Zhou wenjian
> Fix For: 0.94.2
>
> Attachments: HBASE-6537-94.patch, HBASE-6537-94-v2.patch,
> HBASE-6537-trunk.patch
>
>
> Appear in 94. trunk is ok for the issue
> Balancer will collect the regionplans to move(unassign and then assign).
> before unassign, disable table appears,
> after close the region in rs, master will delete the znode, romove region
> from RIT,
> and then clean the region from the online regions.
> During romoving region from RIT and cleaning out the region from the online
> regions.
> balancer begins to unassign, it will get a NotServingRegionException and if
> the table is disabling, it will deal with the state in master and delete the
> znode . However the table is disabled now, so the RIT and znode will remain.
> TimeoutMonitor draws a blank on it.
> It will hold back enabling the table or balancer unless restart
--
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
