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-3292) ConditionalWriterIT#testOffline failed
Date Tue, 04 Nov 2014 23:16:34 GMT

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

Josh Elser commented on ACCUMULO-3292:
--------------------------------------

Ok, I might have an explanation as to what happened:

Master.log
{noformat}
2014-11-03 09:30:09,813 [tableOps.ChangeTableState] DEBUG: Changed table state 1 OFFLINE
2014-11-03 09:30:09,813 [master.EventCoordinator] INFO : Set table state of 1 to OFFLINE
{noformat}

Tserver.log
{noformat} 
2014-11-03 09:30:10,492 [tserver.Tablet] TABLET_HIST: 1<< opened
2014-11-03 09:30:11,157 [tserver.Compactor] DEBUG: Compaction 1<< 2 read | 2 written
|     40 entries/sec |  0.049 secs
2014-11-03 09:30:11,166 [tserver.Tablet] DEBUG: Logs for memory compacted: 1<< host:port/file:///....
2014-11-03 09:30:11,167 [tserver.Tablet] DEBUG: Logs to be destroyed: 1<< host:port/file:///....
2014-11-03 09:30:11,197 [log.TabletServerLogger] DEBUG:  wrote MinC finish  19: writeTime:1ms

2014-11-03 09:30:11,197 [tserver.Tablet] TABLET_HIST: 1<< MinC [memory] -> file:/.../accumulo/tables/1/default_tablet/F0000001.rf
2014-11-03 09:30:11,198 [tserver.Tablet] DEBUG: MinC finish lock 0.00 secs 1<<
2014-11-03 09:30:11,212 [tserver.Tablet] DEBUG: completeClose(saveState=true completeClose=true)
1<<
2014-11-03 09:30:11,427 [tserver.Tablet] TABLET_HIST: 1<< closed
2014-11-03 09:30:11,428 [tserver.TabletServer] DEBUG: Unassigning 1<<@(null,ip-172-31-38-218.ec2.internal:57457[14974fd15e10004],null)
2014-11-03 09:30:11,451 [tserver.TabletServer] INFO : unloaded 1<<
{noformat}

Thus, the table was "offline" before the tablet was even finished being assigned. The interesting
part is the the next test in ConditionalWriterIT had already started by {{2014-11-03 09:30:10,780}}.

The test waited for the table to be offline but that's only the master's state (view) of the
table. The tabletserver was still working and hadn't yet unloaded the tablet for this table.
Need to see how the client got to the tserver in the first place and didn't fail quickly.

> ConditionalWriterIT#testOffline failed
> --------------------------------------
>
>                 Key: ACCUMULO-3292
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-3292
>             Project: Accumulo
>          Issue Type: Bug
>          Components: test
>            Reporter: Josh Elser
>            Assignee: Josh Elser
>             Fix For: 1.6.2, 1.7.0
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> {noformat}
> -------------------------------------------------------------------------------
> Test set: org.apache.accumulo.test.ConditionalWriterIT
> -------------------------------------------------------------------------------
> Tests run: 17, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 94.566 sec <<<
FAILURE! - in org.apache.accumulo.test.ConditionalWriterIT
> testOffline(org.apache.accumulo.test.ConditionalWriterIT)  Time elapsed: 15.974 sec 
<<< FAILURE!
> java.lang.AssertionError: null
> 	at org.junit.Assert.fail(Assert.java:86)
> 	at org.junit.Assert.assertTrue(Assert.java:41)
> 	at org.junit.Assert.assertFalse(Assert.java:64)
> 	at org.junit.Assert.assertFalse(Assert.java:74)
> 	at org.apache.accumulo.test.ConditionalWriterIT.testOffline(ConditionalWriterIT.java:1151)
> {noformat}
> Looks like we somehow didn't get an exception when fetching the status for a ConditionalMutation
written to an offline table.
> Also, need to take the time to ensure that all of the assertions in this class have meaningful
messages as this is the second one in a week that gave no clear reason for its failure.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message