[
https://issues.apache.org/jira/browse/CASSANDRA-1361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16078879#comment-16078879
]
Robin Mahony commented on CASSANDRA-1361:
-----------------------------------------
what about during a recovery scenario? Today if you want to replace a dead seed
node, you need to promote a new seed node first before you bootstrap a node
node in place of the recovered seed node. This means to replace a seed node a
rolling restart of ALL Cassandra nodes is required; which is very extreme for
what should be a simple procedure. I believe that is what this jira description
is all about. Does this not seem like a valid use case for such a feature?
> Introduce ability to change seed addresses on a running node
> ------------------------------------------------------------
>
> Key: CASSANDRA-1361
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1361
> Project: Cassandra
> Issue Type: New Feature
> Reporter: Valentino Volonghi
>
> Since seed nodes are not only used for bootstrap but also for gossiping it
> would be really useful to be able to replace seed addresses on running nodes
> without restarting them since at the moment you can only change seed nodes by
> changing configuration file and then restarting cassandra.
> My usecase is to be able to replace failed seed nodes in cassandra without
> having to proceed to a rolling restart of the cluster. And also to be able to
> start X nodes that initially might be independent but then would all join an
> existing ring by changing their seeds.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
