Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Fri, 31 Aug 2012 14:04:09 +1100 (NCT)
From: "zhou wenjian (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <1845254472.20149.1346382249539.JavaMail.jiratomcat@arcas>
In-Reply-To: <31995003.115620.1343638848911.JavaMail.jiratomcat@issues-vm>
Subject: [jira] [Commented] (HBASE-6473) deleted table is not deleted
 completely, some region may be still online
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

zhou wenjian commented on HBASE-6473:
-------------------------------------

@Lars, i have got the patch for 94.
but since test for trunk is not passed (i do not know why, they are nothing with my case..)
                
> deleted table is not deleted completely, some region may be still online
> ------------------------------------------------------------------------
>
>                 Key: HBASE-6473
>                 URL: https://issues.apache.org/jira/browse/HBASE-6473
>             Project: HBase
>          Issue Type: Bug
>    Affects Versions: 0.94.0
>            Reporter: zhou wenjian
>            Assignee: Zhou wenjian
>             Fix For: 0.96.0, 0.94.2
>
>         Attachments: HBASE-6473-trunk.patch, HBASE-6473-trunk-v2.patch, HBASE-6473-trunk-v3.patch, HBASE-6473-trunk-v4.patch
>
>
> consider such Scenario:
> we have a table called T1, which has 1 regions: A 
> 1. move A from rs1 to rs2,and A is now closed
> 2. disable T1,
> 3. delete  T1.
> when we disable T1, disable handler will just set the zk to disabled and A will still be assigned. when Ais opened, A in transition will be clean out. 
> At that time, Deletetable found it is safe to delete all regions and table in meta and fs , it will also delete the zk node of T1.
> {code}
> while (System.currentTimeMillis() < done) {
>         AssignmentManager.RegionState rs = am.isRegionInTransition(region);
>         if (rs == null) break;
>         Threads.sleep(waitingTimeForEvents);
>         LOG.debug("Waiting on  region to clear regions in transition; " + rs);
>       }
>       if (am.isRegionInTransition(region) != null) {
>         throw new IOException("Waited hbase.master.wait.on.region (" +
>           waitTime + "ms) for region to leave region " +
>           region.getRegionNameAsString() + " in transitions");
>       }
> {code}
> however A is still being unassigned, when it finished closed the A,it finds that the disabled state in zk is deleted, and then A will be assigned again.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira