cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paulo Motta (JIRA)" <>
Subject [jira] [Updated] (CASSANDRA-13056) dtest failure in materialized_views_test.TestMaterializedViews.base_replica_repair_test
Date Mon, 19 Dec 2016 19:13:58 GMT


Paulo Motta updated CASSANDRA-13056:
    Assignee: Paulo Motta
    Reviewer: Philip Thompson
      Status: Patch Available  (was: Open)

It seems I missed this failure when reviewing CASSANDRA-12905. That ticket introduced a new
test {{base_replica_repair_with_contention_test}} which is a special case of {{base_replica_repair_test}}
that needs to update the write timeout and add special JVM options which are not required
by the original {{base_replica_repair_test}}. 

Updating the node's configuration on {{base_replica_repair_with_contention_test}} makes it
refresh and remove itself from the seed list, what requires the use of the {{cassandra.allow_unsafe_replace=true}}
and {{-Dcassandra.replace_address}}. These options are not required in the original {{base_replica_repair_test}}
because the node remains a seed because the configuration is not updated so it will do an
unsafe replace with new tokens.

The fix is simple and basically restores the original behavior of {{base_replica_repair_test}}
by only setting flags and options when {{fail_mv_lock=True}}. Created a [pull request|]
and submitted CI runs:


> dtest failure in materialized_views_test.TestMaterializedViews.base_replica_repair_test
> ---------------------------------------------------------------------------------------
>                 Key: CASSANDRA-13056
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Testing
>            Reporter: Sean McCarthy
>            Assignee: Paulo Motta
>            Priority: Blocker
>              Labels: dtest, test-failure
>             Fix For: 3.10
>         Attachments: node1.log, node1_debug.log, node1_gc.log, node2.log, node2_debug.log,
node2_gc.log, node3.log, node3_debug.log, node3_gc.log
> example failure:
> {code}
> Standard Output
> Unexpected error in node1 log, error: 
> ERROR [main] 2016-12-15 23:40:43,219 - Exception encountered
during startup
> java.lang.RuntimeException: Cannot replace_address / because it doesn't exist
in gossip
> 	at org.apache.cassandra.service.StorageService.prepareForReplacement(
> 	at org.apache.cassandra.service.StorageService.prepareToJoin(
> 	at org.apache.cassandra.service.StorageService.initServer( ~[main/:na]
> 	at org.apache.cassandra.service.StorageService.initServer( ~[main/:na]
> 	at org.apache.cassandra.service.CassandraDaemon.setup( [main/:na]
> 	at org.apache.cassandra.service.CassandraDaemon.activate( [main/:na]
> 	at org.apache.cassandra.service.CassandraDaemon.main( [main/:na]
> {code}{code}
> Stacktrace
>   File "/usr/lib/python2.7/unittest/", line 358, in run
>     self.tearDown()
>   File "/home/automaton/cassandra-dtest/", line 583, in tearDown
>     raise AssertionError('Unexpected error in log, see stdout')
> {code}

This message was sent by Atlassian JIRA

View raw message