[
https://issues.apache.org/jira/browse/HBASE-5894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13264339#comment-13264339
]
xufeng commented on HBASE-5894:
-------------------------------
@Ted
The for loop in HBaseAdmin#deleteTable() cost too long time.
In fact When I verified this patch,My client code spent 50 min until return.
In test,If one test cost more than 900s(the value of
forkedProcessTimeoutInSeconds defined in pom.xml)
then this test will be killed and the others also will not run,is it?
> Delete table failed but HBaseAdmin#deletetable report it as success
> -------------------------------------------------------------------
>
> Key: HBASE-5894
> URL: https://issues.apache.org/jira/browse/HBASE-5894
> Project: HBase
> Issue Type: Bug
> Affects Versions: 0.90.7, 0.92.2, 0.94.0
> Environment: all versions
> Reporter: xufeng
> Assignee: xufeng
> Priority: Minor
> Attachments: HBASE-5894_trunk_patch_v1.patch,
> HBASE-5894_trunk_patch_v1_surefire-report.html
>
>
> Reproduce this issue by following steps:
> For reproduce it I add this code in DeleteTableHandler#handleTableOperation():
> {noformat}
> LOG.debug("Deleting region " + region.getRegionNameAsString() +
> " from META and FS");
> +if (true) {
> + throw new IOException("ERROR");
> +}
> // Remove region from META
> MetaEditor.deleteRegion(this.server.getCatalogTracker(), region);
> {noformat}
> step1:create a table and disable it.
> step2:delete it by HBaseAdmin#deleteTable() API.
> result:after lone time, The log say the Table has been deleted, but in fact
> if we do "list" in shell,the table also exists.
--
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
