hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-7788) [snapshot 130201 merge] Fix flakey TestRestore*SnapshotFromClient#testCloneSnapshot
Date Thu, 07 Feb 2013 14:33:13 GMT

    [ https://issues.apache.org/jira/browse/HBASE-7788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13573539#comment-13573539

Hadoop QA commented on HBASE-7788:

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:green}+1 tests included{color}.  The patch appears to include 3 new or modified

    {color:red}-1 patch{color}.  The patch command could not apply the patch.

Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/4367//console

This message is automatically generated.
> [snapshot 130201 merge] Fix flakey TestRestore*SnapshotFromClient#testCloneSnapshot
> -----------------------------------------------------------------------------------
>                 Key: HBASE-7788
>                 URL: https://issues.apache.org/jira/browse/HBASE-7788
>             Project: HBase
>          Issue Type: Sub-task
>            Reporter: Jonathan Hsieh
>            Assignee: Jonathan Hsieh
>         Attachments: hbase-7788.debug.patch, hbase-7788.patch
> In the current implementation the clone call waits until after the newly created table
isTableEnabled. However there is another state (apparently orthogonal) that a newly created
table is assumed to be – isTableAvailable (all regions assigned). The logic for checking
after table creation and after clone creation are slightly different – creation does the
equivalent of isTableAvailable but clone does not check this availability condition.
> This causes flaky failures in tests that quickly try to use/delete a newly cloned table.
> TestRestoreSnapshotFromClient#testCloneSnapshot
> TestRestoreFlushSnapshotFromCleitn#testCloneSnapshot
> I believe there also are race conditions because of the postTableCreateHandler corpco
and postTableDeleteHandler coproc hooks.

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

View raw message