accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Elser (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-1743) Seeing unexpected trace output
Date Fri, 03 Jan 2014 17:19:57 GMT


Josh Elser commented on ACCUMULO-1743:

Just saw this failure after your changes, [~ecn]. I'm thinking that the trace table wasn't
yet created, got created, but the table cache wasn't updated before we tried to use it and
got the error.

Running org.apache.accumulo.test.ConditionalWriterIT
Tests run: 17, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 21.262 sec <<< FAILURE!
testTrace(org.apache.accumulo.test.ConditionalWriterIT)  Time elapsed: 0.205 sec  <<<
org.apache.accumulo.core.client.TableNotFoundException: Table trace does not exist
	at org.apache.accumulo.core.client.admin.TableOperationsImpl.doFateOperation(
	at org.apache.accumulo.core.client.admin.TableOperationsImpl.doFateOperation(
	at org.apache.accumulo.core.client.admin.TableOperationsImpl.doTableFateOperation(
	at org.apache.accumulo.core.client.admin.TableOperationsImpl.deleteRows(
	at org.apache.accumulo.test.ConditionalWriterIT.testTrace(
	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.junit.runners.model.FrameworkMethod$1.runReflectiveCall(
	at org.junit.runners.model.FrameworkMethod.invokeExplosively(
	at org.junit.internal.runners.statements.InvokeMethod.evaluate(
	at org.junit.internal.runners.statements.FailOnTimeout$
Caused by: ThriftTableOperationException(tableId:null, tableName:trace, op:DELETE_RANGE, type:NOTFOUND,
	at org.apache.accumulo.core.master.thrift.FateService$executeFateOperation_result$
	at org.apache.accumulo.core.master.thrift.FateService$executeFateOperation_result$
	at org.apache.accumulo.core.master.thrift.FateService$
	at org.apache.thrift.TServiceClient.receiveBase(
	at org.apache.accumulo.core.master.thrift.FateService$Client.recv_executeFateOperation(
	at org.apache.accumulo.core.master.thrift.FateService$Client.executeFateOperation(
	at org.apache.accumulo.core.client.admin.TableOperationsImpl.executeFateOperation(
	at org.apache.accumulo.core.client.admin.TableOperationsImpl.doFateOperation(
	... 13 more

> Seeing unexpected trace output
> ------------------------------
>                 Key: ACCUMULO-1743
>                 URL:
>             Project: Accumulo
>          Issue Type: Bug
>          Components: trace
>            Reporter: Keith Turner
>             Fix For: 1.6.0
> While testing ACCUMULO-1608 I was seeing unexpected trace output on the monitor page.
 For example I would see two prep or two wal events when I only expected to see one.  I added
debug stmts on the tserver to verify that wal was only being written to once.   
> Once we figure out what is going on, need to write a trace test for conditional writer.

This message was sent by Atlassian JIRA

View raw message