CODEWITHSUNDEEP
cassandracassandra-2.0cassandra-2.1
Eats
Eats

Reputation: 597

Replacing a seed node without removing it from seed list

I have a cassandra(version 2.2.8) cluster of total 6 nodes, where 3 nodes are seed nodes. One of the seed node recently went down. I need to replace that dead seed node. My cluster is setup in a way where it cannot survive a loss of more than 1 node. I read this documentation to replace the dead seed node. https://docs.datastax.com/en/cassandra/2.1/cassandra/operations/opsReplaceNode.html

As per the documentation, I am scared to remove the dead seed node from the seed list and do a rolling restart. If for any reason any node doesnt start, Ill lose the data.

How to approach this scenario? Is it ok to not remove the dead seed node from the seed list until the new node is fully up and running? As i already have two working seed nodes already present in the seed list. Please advice.

Upvotes: 2

Views: 1481

Answers (1)

Simon Fontana Oscarsson
Simon Fontana Oscarsson

Reputation: 2124

In short: Yes it is okay to wait with removing the seed node.

Explanation: Seed node configuration do two things:

  1. When adding new nodes. The new node will read the seed configuration to get a first contact point to the Cassandra cluster. After the node has joined the cluster it will save information about all Cassandra nodes in it's system.peers table. For all future starts it will use this information to connect to the cluster, not the seed node configuration.
  2. Cassandra also uses seeds as a way to improve gossip. Basically, seed nodes are more likely to receive gossip messages than normal nodes. This improves the speed at which nodes receive updates about other nodes, such as the status.

Losing a seed node will in your case only impact 2. Since you have two more seed nodes I don't see this as a big issue. I would still do a rolling restart on all nodes as soon as you have updated your seed configuration.

Upvotes: 3

Related Questions