This capability was *just* added in CASSANDRA-14190 and only in trunk. Previously (as described in the ticket above), the seed node list is only updated when doing a shadow round, removing an endpoint or restarting (look for callers of o.a.c.gms.Gossiper#buildSeedsList() if you're curious).
A rolling restart is the usual SOP for that. On Fri, Mar 23, 2018 at 9:54 AM, Carl Mueller <carl.muel...@smartthings.com> wrote: > We have a cluster that is subject to the one-year gossip bug. > > We'd like to update the seed node list via JMX without restart, since our > foolishly single-seed-node in this forsaken cluster is being autoculled in > AWS. > > Is this possible? It is not marked volatile in the Config of the source > code, so I doubt it. > -- ----------------- Nate McCall Wellington, NZ @zznate CTO Apache Cassandra Consulting http://www.thelastpickle.com
