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

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Not A Problem
• Component/s: fate
• Labels: newbie
• Assignee: Unassigned
• Reporter: Josh Elser
• Created: 12/May/15 19:17
• Updated: 06/Jan/19 01:14
• Resolved: 06/Jan/19 01:14

Description

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

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)

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.

Issue Links

• is superceded by: ACCUMULO-3925 Remove unnecessary warning messages from FATE ops