IllegalStateException: Active assignment already exists

[mikewalch]

Encountered this exception while running continuous ingest on 1.9 branch.

Thread "tablet assignment 1" died Active assignment already exists for 2;7666c;759a09
	java.lang.IllegalStateException: Active assignment already exists for 2;7666c;759a09
		at org.apache.accumulo.tserver.ActiveAssignmentRunnable.run(ActiveAssignmentRunnable.java:54)
		at org.apache.htrace.wrappers.TraceRunnable.run(TraceRunnable.java:57)
		at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
		at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
		at org.apache.accumulo.fate.util.LoggingRunnable.run(LoggingRunnable.java:35)
		at java.lang.Thread.run(Thread.java:748)

[ctubbsii]

Removed 1.9.2 label in prep for RC1, since it's not marked as a blocker. Also not sure if it's still relevant (or if it was found before or after applying the latest round of @keith-turner 's WAL patches).

[ctubbsii]

@mikewalch Have you seen this lately? Should this be done for 1.9.3?

[mikewalch]

@mikewalch Have you seen this lately? Should this be done for 1.9.3?

No but I haven't run continuous ingest lately. I say hold off on it unless it reappears in testing.

[ctubbsii]

Okay, then I'm bumping it from 1.9.3 so we can prepare for a 1.9.3 release candidate.

[milleruntime]

@mikewalch do you remember if you ran this using a Muchos cluster?

[ctubbsii]

@keith-turner ran a successful continuous ingest run for 1.9.3, so I'm inclined to close this as "cannot reproduce". It can always be re-opened if it's seen again.