[
https://issues.apache.org/jira/browse/CASSANDRA-8436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14238257#comment-14238257
]
Omri Bahumi commented on CASSANDRA-8436:
----------------------------------------
This is exactly what's needed to be discussed.
I initially thought of two approaches:
1. "nodetool markreplacement server-ip/server-id" - marks the node for
replacement, next bootstrapping node will replace it
2. "nodetool removenode dead-node-server-id" - next bootstrapping node will get
its tokens
However, after playing with this a bit today, strange things can happen after
the dead node has been removed and the new node hasn't finished bootstrapping
yet.
What do you think about option 1?
> Replacing a dead node by deleting it and bootstrapping a new one
> ----------------------------------------------------------------
>
> Key: CASSANDRA-8436
> URL: https://issues.apache.org/jira/browse/CASSANDRA-8436
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Omri Bahumi
>
> I brought this subject up in the mailing list, now I'm bringing it up in here.
> I'm trying to automate our Cassandra infrastructure. We're using an
> Autoscaling Group for keeping the Cassandra instances alive.
> After the initial cluster creation, nodes are launched with auto_bootstrap
> enabled.
> I was thinking to automate the process of node deletion (when a node
> terminates) and have the new launched node replace it.
> Reading the documentation, replacing a dead node should be done with
> "-Dcassandra.replace_address=<ip-address>".
> Is deleting the node and bootstrapping a new one a feasible solution?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
