accumulo-notifications mailing list archives

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

    [ https://issues.apache.org/jira/browse/ACCUMULO-1743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13861679#comment-13861679
] 

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.

{noformat}
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  <<<
ERROR!
org.apache.accumulo.core.client.TableNotFoundException: Table trace does not exist
	at org.apache.accumulo.core.client.admin.TableOperationsImpl.doFateOperation(TableOperationsImpl.java:329)
	at org.apache.accumulo.core.client.admin.TableOperationsImpl.doFateOperation(TableOperationsImpl.java:296)
	at org.apache.accumulo.core.client.admin.TableOperationsImpl.doTableFateOperation(TableOperationsImpl.java:1572)
	at org.apache.accumulo.core.client.admin.TableOperationsImpl.deleteRows(TableOperationsImpl.java:550)
	at org.apache.accumulo.test.ConditionalWriterIT.testTrace(ConditionalWriterIT.java:1203)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:606)
	at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47)
	at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
	at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)
	at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
	at org.junit.internal.runners.statements.FailOnTimeout$StatementThread.run(FailOnTimeout.java:74)
Caused by: ThriftTableOperationException(tableId:null, tableName:trace, op:DELETE_RANGE, type:NOTFOUND,
description:null)
	at org.apache.accumulo.core.master.thrift.FateService$executeFateOperation_result$executeFateOperation_resultStandardScheme.read(FateService.java:2895)
	at org.apache.accumulo.core.master.thrift.FateService$executeFateOperation_result$executeFateOperation_resultStandardScheme.read(FateService.java:2872)
	at org.apache.accumulo.core.master.thrift.FateService$executeFateOperation_result.read(FateService.java:2814)
	at org.apache.thrift.TServiceClient.receiveBase(TServiceClient.java:78)
	at org.apache.accumulo.core.master.thrift.FateService$Client.recv_executeFateOperation(FateService.java:144)
	at org.apache.accumulo.core.master.thrift.FateService$Client.executeFateOperation(FateService.java:125)
	at org.apache.accumulo.core.client.admin.TableOperationsImpl.executeFateOperation(TableOperationsImpl.java:252)
	at org.apache.accumulo.core.client.admin.TableOperationsImpl.doFateOperation(TableOperationsImpl.java:305)
	... 13 more
{noformat}

> Seeing unexpected trace output
> ------------------------------
>
>                 Key: ACCUMULO-1743
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-1743
>             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
(v6.1.5#6160)

Mime
View raw message