[jira] Resolved: (CASSANDRA-1361) Introduce ability to change seed addresses on a running node

["Jonathan Ellis (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CASSANDRA-1361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jonathan Ellis resolved CASSANDRA-1361.
---------------------------------------

    Resolution: Not A Problem

the important part of gossip is "pick a random node, send what I know about the cluster to it."  seeds are only special cased at all to make sure that we don't end up with a partitioned cluster.

in other words, I can't think of a reason you should need to change seeds at runtime.

> 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
>          Components: Core
>            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 is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.