[
https://issues.apache.org/jira/browse/CASSANDRA-10578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yuki Morishita updated CASSANDRA-10578:
---------------------------------------
Fix Version/s: (was: 3.0.0)
(was: 2.2.x)
(was: 2.1.x)
> bootstrap_test.py:TestBootstrap.simultaneous_bootstrap_test dtest failing
> -------------------------------------------------------------------------
>
> Key: CASSANDRA-10578
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10578
> Project: Cassandra
> Issue Type: Sub-task
> Reporter: Jim Witschey
> Assignee: Yuki Morishita
>
> This test fails on 2.1, 2.2, and 3.0 versions tested on CassCI:
> http://cassci.datastax.com/view/cassandra-2.1/job/cassandra-2.1_dtest/lastCompletedBuild/testReport/bootstrap_test/TestBootstrap/simultaneous_bootstrap_test/
> http://cassci.datastax.com/view/cassandra-2.2/job/cassandra-2.2_dtest/350/testReport/junit/bootstrap_test/TestBootstrap/simultaneous_bootstrap_test/
> http://cassci.datastax.com/view/cassandra-3.0/job/cassandra-3.0_dtest/lastCompletedBuild/testReport/bootstrap_test/TestBootstrap/simultaneous_bootstrap_test/
> It fails with the same error, indicating that the third node, which should
> not start while another node is bootstrapping, started. Oddly, the assertion
> just before it, looking for a particular error in the logs, succeeds.
> This could be a race condition, where one node successfully completes
> bootstrapping before the third node is started. However, I don't know how
> likely that is, since it fails consistently. Unfortunately, we don't have
> enough history on CassCI to show when the test failure started.
> I'm assigning [~yukim] for now, feel free to reassign.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
