cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jim Witschey (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-10578) bootstrap_test.py:TestBootstrap.simultaneous_bootstrap_test dtest failing
Date Fri, 23 Oct 2015 15:21:28 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-10578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jim Witschey updated CASSANDRA-10578:
-------------------------------------
    Description: 
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. 

  was:
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 started.

I'm assigning [~yukim] for now, feel free to reassign. 


> 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
>             Fix For: 2.1.x, 2.2.x, 3.0.0
>
>
> 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)

Mime
View raw message