Description
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)
Cannot move tables to a new namespace by renaming. The namespace for nspc_000.ctt_002 does not match ctt_001
Lots of WARN messages seen during randomwalk that aren't system-level warning messages. They are perfectly normal and expected. We should not be putting a warning to the monitor for this messages. The exception thrown back to the client is sufficient.
Attachments
Attachments
Issue Links
- supercedes
-
ACCUMULO-3806 Failing to create a table/namespace because it already exists should not be a warning
- Resolved