You are viewing a plain text version of this content. The canonical link for it is here.
Posted to pr@cassandra.apache.org by "rhuffy (via GitHub)" <gi...@apache.org> on 2023/03/14 21:06:00 UTC

[GitHub] [cassandra-dtest] rhuffy opened a new pull request, #215: CASSANDRA-18319: IP change then decommission

rhuffy opened a new pull request, #215:
URL: https://github.com/apache/cassandra-dtest/pull/215

   Adds a new test to reproduce the issue reported in [CASSANDRA-18319](https://issues.apache.org/jira/browse/CASSANDRA-18319).
   
   Decommissioning a node soon after changing its IP causes the old IP to be resurrected and re-added to the token ring.
   
   This test performs the following:
   - creates a 6 node cluster
   - changes the IP of Node6 from `127.0.0.6` to `127.0.0.9`
   - performs a rolling restart on the cluster
   - decommissions Node6
   - asserts that the log `"Node /127.0.0.6 is now part of the cluster"` does not appear after the rolling restart.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: pr-unsubscribe@cassandra.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: pr-unsubscribe@cassandra.apache.org
For additional commands, e-mail: pr-help@cassandra.apache.org