[HBASE-20272] TestAsyncTable#testCheckAndMutateWithTimeRange fails due to TableExistsException

• Type: Test
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.0.0
• Hadoop Flags: Reviewed
• Assignee: Ted Yu
• Reporter: Ted Yu
• Created: 24/Mar/18 02:02
• Updated: 28/Mar/18 02:51
• Resolved: 26/Mar/18 19:55

Description

The following test failure is reproducible:

org.apache.hadoop.hbase.TableExistsException: testCheckAndMutateWithTimeRange
 at org.apache.hadoop.hbase.master.procedure.CreateTableProcedure.prepareCreate(CreateTableProcedure.java:233)
 at org.apache.hadoop.hbase.master.procedure.CreateTableProcedure.executeFromState(CreateTableProcedure.java:87)
 at org.apache.hadoop.hbase.master.procedure.CreateTableProcedure.executeFromState(CreateTableProcedure.java:51)
 at org.apache.hadoop.hbase.procedure2.StateMachineProcedure.execute(StateMachineProcedure.java:184)
 at org.apache.hadoop.hbase.procedure2.Procedure.doExecute(Procedure.java:845)
 at org.apache.hadoop.hbase.procedure2.ProcedureExecutor.execProcedure(ProcedureExecutor.java:1453)

The cause was that TestAsyncTable is parameterized while the testCheckAndMutateWithTimeRange uses the same table name without dropping the table after the first invocation finishes.
This leads to second invocation failing with TableExistsException.

Issue Links

• is related to: HBASE-19504 Add TimeRange support into checkAndMutate