-
Notifications
You must be signed in to change notification settings - Fork 64
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Does the operator handle CASSANDRA-17883? #539
Comments
I assume this is the same as #130 ? |
@burmanm, it seems like a different (although somewhat related) issue. |
What happened?
While reading through open Cassandra issues, I came across CASSANDRA-17883. The issue is that, when a C* node is removed, its IP address gets added to a list of ignoredEndpoints in MigrationCoordinator. In the C* source, there is a TODO comment that describes the issue:
When a pod bounces and comes up with a different IP, the old IP is removed from gossip, and I believe it's also added to ignoredEndpoints. If another pod bounces and gets that original IP, my concern is that any schema changes on that node will be ignored by the rest of the cluster.
Does the operator do anything to handle this situation?
What did you expect to happen?
No response
How can we reproduce it (as minimally and precisely as possible)?
I don't have a repro on a test k8s cluster since I'm not sure how to force pods to come up with particular IPs.
You can, however, reproduce in Cassandra dtests with these steps
Note that if node1 is restarted with some new IP, it will receive the schema change from node2, and pass it along to node3.
cass-operator version
1.15.0
Kubernetes version
1.24
Method of installation
No response
Anything else we need to know?
No response
The text was updated successfully, but these errors were encountered: