Re: cassl 2.1.x seed node update via JMX

What's the "one-year gossip bug" in this context? On Thu, Mar 22, 2018 at 3:26 PM, Carl Mueller wrote: > Thanks. The rolling restart triggers the gossip bug so that's a no go. > We'lre going to migrate off the clsuter. Thanks! > > > > On Thu, Mar 22, 2018 at 5:04

Re: cassl 2.1.x seed node update via JMX

Thanks. The rolling restart triggers the gossip bug so that's a no go. We'lre going to migrate off the clsuter. Thanks! On Thu, Mar 22, 2018 at 5:04 PM, Nate McCall wrote: > This capability was *just* added in CASSANDRA-14190 and only in trunk. > > Previously (as

Re: cassl 2.1.x seed node update via JMX

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

cassl 2.1.x seed node update via JMX

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