cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shawn Kumar (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-8252) dtests that involve topology changes should verify system.peers on all nodes
Date Tue, 21 Apr 2015 18:46:02 GMT

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

Shawn Kumar commented on CASSANDRA-8252:
----------------------------------------

Seems to be a number of failures when I tried incorporating into existing code. To try and
clarify/separate from other tests, I wrote up a separate [dtest|https://github.com/riptano/cassandra-dtest/blob/peerstest/peers_test.py]
to test some basic actions (bootstrapping, removing nodes) and am still running into failures
on all of these. 

> dtests that involve topology changes should verify system.peers on all nodes
> ----------------------------------------------------------------------------
>
>                 Key: CASSANDRA-8252
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-8252
>             Project: Cassandra
>          Issue Type: Test
>          Components: Tests
>            Reporter: Brandon Williams
>            Assignee: Shawn Kumar
>             Fix For: 2.0.15, 2.1.5
>
>
> This is especially true for replace where I've discovered it's wrong in 1.2.19, which
is sad because now it's too late to fix.  We've had a lot of problems with incorrect/null
system.peers, so after any topology change we should verify it on every live node when everything
is finished.



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

Mime
View raw message