Return-Path: X-Original-To: apmail-hbase-issues-archive@www.apache.org Delivered-To: apmail-hbase-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id A37FDDBBD for ; Wed, 15 Aug 2012 14:00:56 +0000 (UTC) Received: (qmail 76912 invoked by uid 500); 15 Aug 2012 14:00:56 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 76880 invoked by uid 500); 15 Aug 2012 14:00:56 -0000 Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@hbase.apache.org Received: (qmail 76864 invoked by uid 99); 15 Aug 2012 14:00:56 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 15 Aug 2012 14:00:56 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id D07482C5BE7 for ; Wed, 15 Aug 2012 14:00:55 +0000 (UTC) Date: Thu, 16 Aug 2012 01:00:55 +1100 (NCT) From: "Zhihong Ted Yu (JIRA)" To: issues@hbase.apache.org Message-ID: <672183455.13539.1345039255854.JavaMail.jiratomcat@arcas> In-Reply-To: <31995003.115620.1343638848911.JavaMail.jiratomcat@issues-vm> Subject: [jira] [Updated] (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 X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HBASE-6473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhihong Ted Yu updated HBASE-6473: ---------------------------------- Summary: deleted table is not deleted completely, some region may be still online (was: deletedtable is not deleted completely, some region may be still online) > 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 > Fix For: 0.96.0, 0.94.2 > > Attachments: HBASE-6473-trunk.patch, HBASE-6473-trunk-v2.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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira