[ https://issues.apache.org/jira/browse/HBASE-6473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13427083#comment-13427083 ]
Zhou wenjian commented on HBASE-6473: ------------------------------------- @Jimmy Xiang. You mean check the region state in rit to see it is offline? Region maybe is not in rit when delete table occours. And i do not quite follow the reason we check the region in rit offline. Do you have a email? I suggest we discuss it personally > deletedtable 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 > > > 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