[ https://issues.apache.org/jira/browse/HBASE-7788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Hsieh reassigned HBASE-7788: ------------------------------------- Assignee: Jonathan Hsieh > [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 > > 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