You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2013/05/20 20:01:20 UTC

[jira] [Reopened] (HBASE-8067) TestHFileArchiving.testArchiveOnTableDelete sometimes fails

     [ https://issues.apache.org/jira/browse/HBASE-8067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

stack reopened HBASE-8067:
--------------------------


Was going to open a new issue after this test failed on the first build after its commit but instead, will just do reopen of this one again (the second time).

Here is the fail: http://54.241.6.143/job/HBase-0.95/org.apache.hbase$hbase-server/294/
                
> TestHFileArchiving.testArchiveOnTableDelete sometimes fails
> -----------------------------------------------------------
>
>                 Key: HBASE-8067
>                 URL: https://issues.apache.org/jira/browse/HBASE-8067
>             Project: HBase
>          Issue Type: Bug
>          Components: Admin, master, test
>    Affects Versions: 0.94.6, 0.95.2
>            Reporter: Matteo Bertozzi
>            Assignee: Matteo Bertozzi
>             Fix For: 0.98.0, 0.94.8, 0.95.1
>
>         Attachments: 8067-0.94.txt, 8067-trunk.txt, HBASE-8067-debug.patch, HBASE-8067-v0.patch
>
>
> it seems that testArchiveOnTableDelete() fails because the archiving in DeleteTableHandler is still in progress when admin.deleteTable() returns.
> {code}
> Error Message
> Archived files are missing some of the store files!
> Stacktrace
> java.lang.AssertionError: Archived files are missing some of the store files!
> 	at org.junit.Assert.fail(Assert.java:88)
> 	at org.junit.Assert.assertTrue(Assert.java:41)
> 	at org.apache.hadoop.hbase.backup.TestHFileArchiving.testArchiveOnTableDelete(TestHFileArchiving.java:262)
> {code}
> (Looking at the problem in a more generic way, we don't have any way to inform the client when an async operation is completed)

--
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