Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Mon, 13 Aug 2012 16:08:38 +1100 (NCT)
From: "Zhou wenjian (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <1965890004.550.1344834518015.JavaMail.jiratomcat@arcas>
Subject: [jira] [Commented] (HBASE-6537) Balancer compete with disable table
 will lead to cluster inconsistent
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HBASE-6537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13432921#comment-13432921 ] 

Zhou wenjian commented on HBASE-6537:
-------------------------------------

@Ted
we have no trunk hudson, just 94 in local
                
> 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