This Kubernetes operator automates the Cassandra operations such as deploying a new rack aware cluster, adding/removing nodes, configuring the C* and JVM parameters, upgrading JVM and C* versions, and many more...
When a node is live it's considered as ready and the next node is started, however the bootstrap of the next node will fail cause native protocol is not enable yet.
What did you do?
Create a new cluster with 2 nodes and check if nodes see each other or not. It happens that they belong to different rings.
What did you expect to see?
the bootstrap image tries to access the native port of seed nodes to know if they can join an existing ring. But as a node is ready before it can happen that they don't see each other.
What did you see instead? Under which circumstances?
nodes do not see each other
Environment
casskop version: 1.1.2
Possible Solution
Test the JMX port instead of the native port.
Bug Report
When a node is live it's considered as ready and the next node is started, however the bootstrap of the next node will fail cause native protocol is not enable yet.
What did you do? Create a new cluster with 2 nodes and check if nodes see each other or not. It happens that they belong to different rings.
What did you expect to see? the bootstrap image tries to access the native port of seed nodes to know if they can join an existing ring. But as a node is ready before it can happen that they don't see each other.
What did you see instead? Under which circumstances? nodes do not see each other
Environment
Possible Solution Test the JMX port instead of the native port.