[
https://issues.apache.org/jira/browse/HBASE-20272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16412787#comment-16412787
]
Ted Yu commented on HBASE-20272:
--------------------------------
bq. No reference to the issue that caused the problem
When I logged the JIRA, I was looking at why the TableExistsException happened
in the test.
I didn't look at git log closely to see which commit resulted in the test
failure.
Later I realized this was a regression. By the time I was about to link to
related issue, you already added the link (I needed to drive my kids to various
activities on Saturday).
Thanks for adding the link to the related issue, BTW.
bq. Why not just do an addendum on the original?
See above - I didn't pinpoint the related issue in the first place. I also
didn't want to cause confusion in case wrong issue was identified.
I will refer to the history more closely and use addendum on the original issue
in the future for test breakage.
> TestAsyncTable#testCheckAndMutateWithTimeRange fails due to
> TableExistsException
> --------------------------------------------------------------------------------
>
> Key: HBASE-20272
> URL: https://issues.apache.org/jira/browse/HBASE-20272
> Project: HBase
> Issue Type: Test
> Reporter: Ted Yu
> Assignee: Ted Yu
> Priority: Major
> Attachments: 20272.v1.txt, 20272.v2.txt
>
>
> The following test failure is reproducible:
> {code}
> 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)
> {code}
> 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.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
