[
https://issues.apache.org/jira/browse/CASSANDRA-11360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sam Tunnicliffe updated CASSANDRA-11360:
----------------------------------------
Status: Awaiting Feedback (was: Open)
CASSANDRA-11038 removed the erroneous {{NEW_NODE}} notification fired on
restart of an existing node. However, it was only committed to 2.2+ and the
corresponding [dtest
changes|https://github.com/riptano/cassandra-dtest/pull/983] didn't include any
logic to expect the old behaviour on 2.1, hence the test failures. I've opened
a new [dtest pr|https://github.com/riptano/cassandra-dtest/pull/1122] to add
that and I'll resolve this issue when that PR gets merged.
> dtest failure in
> pushed_notifications_test.TestPushedNotifications.restart_node_test
> ------------------------------------------------------------------------------------
>
> Key: CASSANDRA-11360
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11360
> Project: Cassandra
> Issue Type: Bug
> Reporter: Jim Witschey
> Assignee: Sam Tunnicliffe
> Labels: dtest
>
> This has flaked on the 2.1 offheap memtables job several times. This is the
> most recent failure:
> http://cassci.datastax.com/job/cassandra-2.1_offheap_dtest/318/testReport/pushed_notifications_test/TestPushedNotifications/restart_node_test
> But it's different from the other recent failures:
> http://cassci.datastax.com/job/cassandra-2.1_offheap_dtest/303/testReport/junit/pushed_notifications_test/TestPushedNotifications/restart_node_test/
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
