[ 
https://issues.apache.org/jira/browse/ACCUMULO-3135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14144965#comment-14144965
 ] 

Josh Elser commented on ACCUMULO-3135:
--------------------------------------

bq. It does not seem like anyone would be relying on the current behavior. 

I certainly hope not :). The likelihood of this happening in a "real" system is 
probably very small as well (tables usually are long-lived things). The window 
to actually hit this bug and not get the proper exception (table is deleted 
after fetching the table Id using the table name but before the fate op kicks 
in). I feel comfortable with it.

I'll let this open today for some extra feedback if anyone has it while I clean 
up the changes to minimize repetition.

> RW concurrent test failed with table exist exception
> ----------------------------------------------------
>
>                 Key: ACCUMULO-3135
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-3135
>             Project: Accumulo
>          Issue Type: Bug
>    Affects Versions: 1.5.0, 1.5.1, 1.6.0
>         Environment: Running RW test against 1.5.2 RC1
>            Reporter: Keith Turner
>            Assignee: Josh Elser
>             Fix For: 1.5.3, 1.6.2, 1.7.0
>
>         Attachments: 
> 0001-ACCUMULO-3135-Modify-server-side-table-operations-to.patch
>
>
> Saw the following error when running RW test against 1.5.2 RC1.  
> {noformat}
> 16 18:34:56,869 [server.Accumulo] INFO : Zookeeper connected and initialized, 
> attemping to talk to HDFS
>         at java.lang.reflect.Method.invoke(Method.java:606)
>         at org.apache.accumulo.start.Main$1.run(Main.java:107)
>         at java.lang.Thread.run(Thread.java:744)
> Caused by: java.lang.Exception: Error running node ct.CloneTable
>         at org.apache.accumulo.test.randomwalk.Module.visit(Module.java:285)
>         at org.apache.accumulo.test.randomwalk.Module.visit(Module.java:254)
>         ... 8 more
> Caused by: org.apache.accumulo.core.client.AccumuloSecurityException: Error 
> TABLE_DOESNT_EXIST for user root - Unknown security exception
>         at 
> org.apache.accumulo.core.client.admin.TableOperationsImpl.doTableOperation(TableOperationsImpl.java:298)
>         at 
> org.apache.accumulo.core.client.admin.TableOperationsImpl.doTableOperation(TableOperationsImpl.java:280)
>         at 
> org.apache.accumulo.core.client.admin.TableOperationsImpl.clone(TableOperationsImpl.java:688)
>         at 
> org.apache.accumulo.test.randomwalk.concurrent.CloneTable.visit(CloneTable.java:48)
>         at org.apache.accumulo.test.randomwalk.Module.visit(Module.java:254)
>         ... 9 more
> Caused by: ThriftSecurityException(user:root, code:TABLE_DOESNT_EXIST)
>         at 
> org.apache.accumulo.core.master.thrift.MasterClientService$executeTableOperation_result$executeTableOperation_resultStandardScheme.read(MasterClientService.java:16120)
>         at 
> org.apache.accumulo.core.master.thrift.MasterClientService$executeTableOperation_result$executeTableOperation_resultStandardScheme.read(MasterClientService.java:16106)
>         at 
> org.apache.accumulo.core.master.thrift.MasterClientService$executeTableOperation_result.read(MasterClientService.java:16048)
>         at 
> org.apache.thrift.TServiceClient.receiveBase(TServiceClient.java:78)
>         at 
> org.apache.accumulo.core.master.thrift.MasterClientService$Client.recv_executeTableOperation(MasterClientService.java:499)
>         at 
> org.apache.accumulo.core.master.thrift.MasterClientService$Client.executeTableOperation(MasterClientService.java:480)
>         at 
> org.apache.accumulo.core.client.admin.TableOperationsImpl.executeTableOperation(TableOperationsImpl.java:236)
>         at 
> org.apache.accumulo.core.client.admin.TableOperationsImpl.doTableOperation(TableOperationsImpl.java:289)
> {noformat}
> Looking at the test code, it specifically checks for 
> {{TableNotFoundException}}, but its getting a 
> {{ThriftSecurityException(user:root, code:TABLE_DOESNT_EXIST)}}.  Need to 
> figure out if this is change in behavior since 1.5.1.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to