[jira] [Created] (ACCUMULO-3806) Failing to create a table/namespace because it already exists should not be a warning

[Josh Elser (JIRA)]

Josh Elser created ACCUMULO-3806:
------------------------------------

             Summary: Failing to create a table/namespace because it already 
exists should not be a warning
                 Key: ACCUMULO-3806
                 URL: https://issues.apache.org/jira/browse/ACCUMULO-3806
             Project: Accumulo
          Issue Type: Improvement
          Components: fate
            Reporter: Josh Elser
             Fix For: 1.6.3, 1.8.0, 1.7.1


This is a really common occurrence when you're running randomwalk:

{noformat}
Failed to execute Repo, tid=63d0421f1b17b04a
        ThriftTableOperationException(tableId:null, tableName:nspc_001.ctt_000, 
op:CREATE, type:EXISTS, description:null)
                at 
org.apache.accumulo.master.tableOps.Utils.checkTableDoesNotExist(Utils.java:54)
                at 
org.apache.accumulo.master.tableOps.PopulateZookeeper.call(PopulateZookeeper.java:54)
                at 
org.apache.accumulo.master.tableOps.PopulateZookeeper.call(PopulateZookeeper.java:30)
                at 
org.apache.accumulo.master.tableOps.TraceRepo.call(TraceRepo.java:57)
                at 
org.apache.accumulo.fate.Fate$TransactionRunner.run(Fate.java:72)
                at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
                at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
                at 
org.apache.accumulo.fate.util.LoggingRunnable.run(LoggingRunnable.java:35)
                at java.lang.Thread.run(Thread.java:745)
{noformat}

Concurrent table creations run: only one succeeds and the others fail. This is 
expected and what FATE was designed to handle. We shouldn't be pushing these up 
to the monitor -- should probably be a info or debug message.



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