[jira] [Updated] (HBASE-20272) TestAsyncTable#testCheckAndMutateWithTimeRange fails due to TableExistsException

2018-03-26 Thread Ted Yu (JIRA) 

 [ 
https://issues.apache.org/jira/browse/HBASE-20272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ted Yu updated HBASE-20272:
---
   Resolution: Fixed
 Hadoop Flags: Reviewed
Fix Version/s: 2.0.0
   Status: Resolved  (was: Patch Available)

> 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
> Fix For: 2.0.0
>
> 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)

[jira] [Updated] (HBASE-20272) TestAsyncTable#testCheckAndMutateWithTimeRange fails due to TableExistsException

2018-03-23 Thread Ted Yu (JIRA) 

 [ 
https://issues.apache.org/jira/browse/HBASE-20272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ted Yu updated HBASE-20272:
---
Attachment: 20272.v2.txt

> 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)

[jira] [Updated] (HBASE-20272) TestAsyncTable#testCheckAndMutateWithTimeRange fails due to TableExistsException

2018-03-23 Thread Ted Yu (JIRA) 

 [ 
https://issues.apache.org/jira/browse/HBASE-20272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ted Yu updated HBASE-20272:
---
Attachment: 20272.v1.txt

> 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
>
>
> 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)

[jira] [Updated] (HBASE-20272) TestAsyncTable#testCheckAndMutateWithTimeRange fails due to TableExistsException

2018-03-23 Thread Ted Yu (JIRA) 

 [ 
https://issues.apache.org/jira/browse/HBASE-20272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ted Yu updated HBASE-20272:
---
Status: Patch Available  (was: Open)

> 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
>
>
> 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)