[jira] [Updated] (CASSANDRA-8252) dtests that involve topology changes should verify system.peers on all nodes
[ https://issues.apache.org/jira/browse/CASSANDRA-8252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] T Jake Luciani updated CASSANDRA-8252: -- Fix Version/s: (was: 2.0.15) 2.0.x > 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.1.x, 2.0.x > > > 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)
[jira] [Updated] (CASSANDRA-8252) dtests that involve topology changes should verify system.peers on all nodes
[ https://issues.apache.org/jira/browse/CASSANDRA-8252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carl Yeksigian updated CASSANDRA-8252: -- Fix Version/s: 2.0.15 > 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.6 > > > 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)
[jira] [Updated] (CASSANDRA-8252) dtests that involve topology changes should verify system.peers on all nodes
[ https://issues.apache.org/jira/browse/CASSANDRA-8252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brandon Williams updated CASSANDRA-8252: Fix Version/s: 2.0.15 > 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)
[jira] [Updated] (CASSANDRA-8252) dtests that involve topology changes should verify system.peers on all nodes
[ https://issues.apache.org/jira/browse/CASSANDRA-8252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brandon Williams updated CASSANDRA-8252: Component/s: Tests Fix Version/s: 2.0.13 2.1.3 > 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.1.3, 2.0.13 > > > 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)
[jira] [Updated] (CASSANDRA-8252) dtests that involve topology changes should verify system.peers on all nodes
[ https://issues.apache.org/jira/browse/CASSANDRA-8252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Philip Thompson updated CASSANDRA-8252: --- Assignee: Shawn Kumar > 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 >Reporter: Brandon Williams >Assignee: Shawn Kumar > > 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)
[jira] [Updated] (CASSANDRA-8252) dtests that involve topology changes should verify system.peers on all nodes
[ https://issues.apache.org/jira/browse/CASSANDRA-8252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brandon Williams updated CASSANDRA-8252: Description: 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. (was: 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 very it on every live node when everything is finished.) > 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 >Reporter: Brandon Williams > > 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)
