[HBASE-7788] [snapshot 130201 merge] Fix flakey TestRestore*SnapshotFromClient#testCloneSnapshot

• Type: Sub-task
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.95.0
• Hadoop Flags: Reviewed
• Assignee: Jonathan Hsieh
• Reporter: Jonathan Hsieh
• Created: 07/Feb/13 14:09
• Updated: 23/Sep/13 18:31
• Resolved: 07/Feb/13 23:06

Description

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.

Issue Links

• depends upon: HBASE-7365 Safer table creation and deletion using .tmp dir