Hello, I think that’s not the optimal way to handle it.
If you are just attaching the same EBS volume to a new node you can do like this: 1) nodetool drain on old 2) stop cassandra on old 3) Attach EBS to new node 4) Start Cassandra on new node Cassandra automatically realizes that have just effectively changed IP address. replace_address will also stream all the data, so that’s inefficient way to do it if you already have all the data. Hannu On 13 June 2017 at 11:23:56, Rutvij Bhatt ([email protected]) wrote: Hi! We're running a Cassandra cluster on AWS. I want to replace an old node with EBS storage with a new one. The steps I'm following are as follows and I want to get a second opinion on whether this is the right thing to do: 1. Remove old node from gossip. 2. Run nodetool drain 3. Stop cassandra 4. Create new new node and update JVM_OPTS in cassandra-env.sh with cassandra.replace_address=<address of node being replaced> as instructed here - http://docs.datastax.com/en/cassandra/2.1/cassandra/operations/opsReplaceNode.html 5. Attach the EBS volume from the old node at the same mount point. 6. Start cassandra on the new node. 7. Run nodetool repair to catch the replacing node up on whatever it has missed. Thanks!
