cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Branimir Lambov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-11811) dtest failure in snapshot_test.TestArchiveCommitlog.test_archive_commitlog
Date Tue, 26 Jul 2016 11:27:21 GMT

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

Branimir Lambov commented on CASSANDRA-11811:
---------------------------------------------

My understanding of the problem is that the second time the cluster was spawned it somehow
got a different configuration. Not surprisingly, restoring the snapshot then failed.

There doesn't seem to be anything wrong with the test, though, it does set the number of vnodes
properly in both cluster creation calls. I don't know how to treat this other than to say
that it is some random failure (something temporarily broke in the infrastructure?), especially
since for all the known history of this test it failed only on this specific run.

> dtest failure in snapshot_test.TestArchiveCommitlog.test_archive_commitlog
> --------------------------------------------------------------------------
>
>                 Key: CASSANDRA-11811
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-11811
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Philip Thompson
>            Assignee: Branimir Lambov
>              Labels: dtest, windows
>             Fix For: 3.x
>
>
> example failure:
> http://cassci.datastax.com/job/trunk_dtest_win32/416/testReport/snapshot_test/TestArchiveCommitlog/test_archive_commitlog
> Failed on CassCI build trunk_dtest_win32 #416
> Relevant error is pasted. This is clearly a test problem. No idea why it only happens
on windows, as of yet. Affecting most tests in the TestArchiveCommitlog suite
> {code}
> WARN: Failed to flush node: node1 on shutdown.
> Unexpected error in node1 log, error: 
> ERROR [main] 2016-05-13 21:15:02,701 CassandraDaemon.java:729 - Fatal configuration error
> org.apache.cassandra.exceptions.ConfigurationException: Cannot change the number of tokens
from 64 to 32
> 	at org.apache.cassandra.service.StorageService.joinTokenRing(StorageService.java:1043)
~[main/:na]
> 	at org.apache.cassandra.service.StorageService.initServer(StorageService.java:740) ~[main/:na]
> 	at org.apache.cassandra.service.StorageService.initServer(StorageService.java:625) ~[main/:na]
> 	at org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:368) [main/:na]
> 	at org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:583) [main/:na]
> 	at org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:712) [main/:na]
> {code}



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

Mime
View raw message