accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Elser (JIRA)" <>
Subject [jira] [Created] (ACCUMULO-3832) Lots of spam on concurrent table deletions in the monitor
Date Tue, 19 May 2015 18:33:00 GMT
Josh Elser created ACCUMULO-3832:

             Summary: Lots of spam on concurrent table deletions in the monitor
                 Key: ACCUMULO-3832
             Project: Accumulo
          Issue Type: Improvement
          Components: master
            Reporter: Josh Elser
            Priority: Minor
             Fix For: 1.8.0, 1.7.1

We're all very used to seeing something like the following in the monitor when running randomwalk:

Failed to execute Repo, tid=4a9b2c5dea42ab5b
	java.lang.IllegalArgumentException: Table with id 10 does not exist
		at org.apache.accumulo.core.client.impl.Tables.getNamespaceId(
		at org.apache.accumulo.master.tableOps.DeleteTable.isReady(
		at org.apache.accumulo.master.tableOps.DeleteTable.isReady(
		at org.apache.accumulo.master.tableOps.TraceRepo.isReady(
		at org.apache.accumulo.fate.Fate$
		at java.util.concurrent.ThreadPoolExecutor.runWorker(
		at java.util.concurrent.ThreadPoolExecutor$

We know that we can ignore it because it's just FATE doing the right thing -- we wanted to
delete a table, but it's already deleted, so there's nothing to do. Super.

The issue is that a less-experienced user might not realize that they can ignore this message.
I think that in the DeleteTable FATE op, it would make sense to fail quietly when we try to
delete something that is already gone. Yes, it is still deserving of an INFO or DEBUG message,
but I don't think this should propagate up to the monitor.

This message was sent by Atlassian JIRA

View raw message