Maintenance

With most databases, there are a number of routine and ad hoc activities to be completed periodically. Apache Cassandra is no exception.

Replacing a node

Sometimes, instead of removing a bad node and adding a new one, you want to replace a node. In larger clusters, this becomes important, in that a new node can be designated as a replacement to a prior, down node. This means that, when the node starts up, it will contact the seed nodes and receive the same token ranges as the previous node.

Let's say that 192.168.0.103 goes down, and I need to replace it. I can re-instance a new node, say, 192.168.0.105. To ensure that 105 gets the same token ranges as 103 had, I can add this one line to the end of the cassandra...