[
https://issues.apache.org/jira/browse/CASSANDRA-8436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14238191#comment-14238191
]
Philip Thompson commented on CASSANDRA-8436:
--------------------------------------------
I don't think it makes sense for Cassandra to automatically replace missing
nodes with the new nodes. It certainly violates least surprise.
Consider the circumstance that a node is down temporarily. This change would
mean that if an operator added a new node while the first node is down, it
would be automatically replaced. Such decisions should always be explicit.
> 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)
