[
https://issues.apache.org/jira/browse/HBASE-5894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13269019#comment-13269019
]
Hadoop QA commented on HBASE-5894:
----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12525738/HBASE-5894_trunk_patch_v3.patch
against trunk revision .
+1 @author. The patch does not contain any @author tags.
-1 tests included. The patch doesn't appear to include any new or modified
tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
+1 hadoop23. The patch compiles against the hadoop 0.23.x profile.
+1 javadoc. The javadoc tool did not generate any warning messages.
+1 javac. The applied patch does not increase the total number of javac
compiler warnings.
+1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9)
warnings.
+1 release audit. The applied patch does not increase the total number of
release audit warnings.
-1 core tests. The patch failed these unit tests:
org.apache.hadoop.hbase.regionserver.TestServerCustomProtocol
org.apache.hadoop.hbase.master.TestSplitLogManager
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/1780//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/1780//artifact/trunk/patchprocess/newPatchFindbugsWarnings.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/1780//console
This message is automatically generated.
> 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_90_patch_v1.patch,
> HBASE-5894_90_patch_v1_surefire-report.html, HBASE-5894_90_patch_v2.patch,
> HBASE-5894_92_patch_v1.patch, HBASE-5894_92_patch_v1_surefire-report.html,
> HBASE-5894_92_patch_v2.patch, HBASE-5894_94_patch_v1.patch,
> HBASE-5894_94_patch_v1_surefire-report.html, HBASE-5894_94_patch_v2.patch,
> HBASE-5894_trunk_patch_v1.patch,
> HBASE-5894_trunk_patch_v1_surefire-report.html,
> HBASE-5894_trunk_patch_v2.patch,
> HBASE-5894_trunk_patch_v2_surefire-report.html,
> HBASE-5894_trunk_patch_v3.patch
>
>
> 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
