[ACCUMULO-4533] TraceServer should not abort if trace table exists

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.7.1, 1.7.2, 1.8.0
• Fix Version/s: 1.7.3, 1.8.1, 2.0.0
• Component/s: trace

Environment

impacts 1.7.0-1.7.2, 1.8.0

• Assignee: Sean Busbey
• Reporter: Sean Busbey
• Created: 07/Dec/16 15:33
• Updated: 10/Feb/17 22:45
• Resolved: 10/Feb/17 22:45

Description

description

On start up, the TraceServer attempts to ensure that the trace table exists.

        connector = serverConfiguration.getInstance().getConnector(principal, at);
        if (!connector.tableOperations().exists(tableName)) {
          connector.tableOperations().create(tableName);
          IteratorSetting setting = new IteratorSetting(10, "ageoff", AgeOffFilter.class.getName());
          AgeOffFilter.setTTL(setting, 7 * 24 * 60 * 60 * 1000l);
          connector.tableOperations().attachIterator(tableName, setting);
        }

The race condition between checking existence and creating the table ought not matter, since we're in a big loop that is supposed to retry on any problems.

However, that loop expressly catches RuntimeException and TableExistsException is not a RuntimeException so currently the exception propagates and kills the server.

workaround

restart any failed trace servers, since the one that won the race condition should have finished set up properly.

alternatively, manually create the trace table prior to starting any trace servers.

Issue Links

• is broken by: ACCUMULO-3643 Find more bugs with findbugs