You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "rajeshbabu (JIRA)" <ji...@apache.org> on 2012/08/09 16:38:19 UTC
[jira] [Commented] (HBASE-6537) Balancer compete with disable table
will lead to cluster inconsistent
[ https://issues.apache.org/jira/browse/HBASE-6537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13431847#comment-13431847 ]
rajeshbabu commented on HBASE-6537:
-----------------------------------
@Zhou wenjian
clearing from online regions before removing from RIT may not solve the problem completely.
Its better to check whether table is in disabling and disabled also in case of NotServingRegionException.
May be this is applicable for trunk also because there also we are checking table is in disabling only.
Please correct me if i am wrong.
> 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.1
>
> Attachments: HBASE-6537-94.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