accumulo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Keith Turner (JIRA)" <>
Subject [jira] [Created] (ACCUMULO-667) Unexpected table not found exception
Date Mon, 02 Jul 2012 20:56:35 GMT
Keith Turner created ACCUMULO-667:

             Summary: Unexpected table not found exception
                 Key: ACCUMULO-667
             Project: Accumulo
          Issue Type: Bug
    Affects Versions: 1.4.0
            Reporter: Keith Turner

While running random walk test to kick the tires on a bulk import bug fix, I ran into the
following error.

02 16:12:41,389 [randomwalk.Framework] ERROR: Error during random walk
java.lang.Exception: Error running node Image.xml
        at org.apache.accumulo.server.test.randomwalk.Module.visit(
        at org.apache.accumulo.server.test.randomwalk.Framework.main(
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(
        at java.lang.reflect.Method.invoke(
        at org.apache.accumulo.start.Main$
Caused by: org.apache.accumulo.core.client.TableNotFoundException: Table img_n_17502_1341245561116
does not exist
        at org.apache.accumulo.core.client.impl.Tables.getTableId(
        at org.apache.accumulo.core.client.admin.TableOperationsImpl.addSplits(
        at org.apache.accumulo.server.test.randomwalk.image.ImageFixture.setUp(
        at org.apache.accumulo.server.test.randomwalk.Module.visit(
        at org.apache.accumulo.server.test.randomwalk.Module.visit(
        ... 8 more

This exception corresponds to the following test code.  So addSplits() was called immediately
after createTable() and did not see the table.  

 try {
      conn.tableOperations().addSplits(imageTableName, splits);   //line 319
      log.debug("Created table " + imageTableName + " (id:" + Tables.getNameToIdMap(instance).get(imageTableName)
+ ")");
    } catch (TableExistsException e) {
      log.error("Table " + imageTableName + " already exists.");
      throw e;

Saw the following in the master logs. The time on the machines involved is off a few seconds.
so the time discrepency does not indicate that the create table operation did not wait before

02 16:12:43,063 [tableOps.Utils] INFO : table 16a (246815aaec0229bc) unlocked for write
02 16:12:43,063 [master.EventCoordinator] INFO : Created table img_n_17502_1341245561116
02 16:12:43,063 [tableOps.FinishCreateTable] DEBUG: Created table 16a img_n_17502_1341245561116

This could be a bug in ZooCache or maybe ZooCache needs to make a zookeeper sync() call before
reading data.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message