[
https://issues.apache.org/jira/browse/ACCUMULO-2092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13856458#comment-13856458
]
Christopher Tubbs commented on ACCUMULO-2092:
---------------------------------------------
No, we believe the problem is that createTable fails because the table exists,
but it's Tables cache isn't updated, so it doesn't actually see that the table
exists when it checks zookeeper itself. A related problem is ACCUMULO-2093.
What needs to happen is that the Tables cache needs to be cleared after every
table/fate operation.
> Seeing spurious error message about namespace that does not exist
> -----------------------------------------------------------------
>
> Key: ACCUMULO-2092
> URL: https://issues.apache.org/jira/browse/ACCUMULO-2092
> Project: Accumulo
> Issue Type: Bug
> Environment: db746960fbcafb1651c15ec2e5493d56acb5065c
> Reporter: Keith Turner
> Fix For: 1.6.0
>
>
> In the conditional random walk test the following spurious error message
> occurred. The test did not fail, it was running fine.
> {noformat}
> 24 17:43:45,065 [conditional.Setup] DEBUG: created table banks
> 24 17:43:45,101 [conditional.Setup] DEBUG: set table.cache.block.enable false
> 24 17:43:45,148 [impl.Tables] ERROR: Table (d) contains reference to
> namespace () that doesn't exist
> 24 17:43:47,012 [conditional.Init] DEBUG: Added splits [b100, b200, b300,
> b400, b500, b600, b700, b800, b900]
> 24 17:44:00,394 [conditional.Init] DEBUG: Added bank b259 9
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
