This Kubernetes operator automates Cassandra operations such as deploying rack aware clusters, scaling up and down, configuring C* and its JVM, upgrading JVM and C*, backup/restores and many more...
What did you do?
During replacement of Cassandra node newly created pod couldn't be added to existing cassandra cluster
'/bootstrap/libs/jolokia-agent.jar' -> '/extra-lib/jolokia-agent.jar'
'//bootstrap/tools/curl' -> '/opt/bin/curl'
== We execute bootstrap script run.sh
CASSANDRA_SEEDS=tf-cassandra-config-dc1-rack1-0.tf-cassandra-config.tf,tf-cassandra-config-dc1-rack1-1.tf-cassandra-config.tf,tf-cassandra-config-dc1-rack1-2.tf-cassandra-config.tf
Try to connect to tf-cassandra-config-dc1-rack1-0.tf-cassandra-config.tf
nc: getaddrinfo for host "tf-cassandra-config-dc1-rack1-0.tf-cassandra-config.tf" port 8778: Temporary failure in name resolution
What did you expect to see?
Bootstrap should exit and retry to add node in case of DNS unavailability.
What did you see instead? Under which circumstances?
Node started as a new cluster.
Environment
casskop version: latest
Possible Solution
Check for DNS error in bootstrap.sh
Bug Report
What did you do? During replacement of Cassandra node newly created pod couldn't be added to existing cassandra cluster
What did you expect to see? Bootstrap should exit and retry to add node in case of DNS unavailability.
What did you see instead? Under which circumstances? Node started as a new cluster.
Environment
Possible Solution Check for DNS error in bootstrap.sh