Noticed this while running randomwalk against 1.8.0-SNAPSHOT. The
monitor's aggregated log messages were just filled with things like the
following:
Failed to execute Repo, tid=76367ba00e847e10
ThriftTableOperationException(tableId:null, tableName: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:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at
org.apache.accumulo.fate.util.LoggingRunnable.run(LoggingRunnable.java:35)
at java.lang.Thread.run(Thread.java:745)
Now, this is happening because of the concurrent module renaming tests,
but is this really a warning that we want to propagate to the monitor?
Everything is just fine and dandy in the system. Doesn't seem like it
really needs to be a warning. Similarly, the following also falls into
the same bucket.
Cannot move tables to a new namespace by renaming. The namespace for
nspc_000.ctt_002 does not match ctt_001
Thoughts before I open an issue to change them?
- Josh
