system.local uses local strategy . You need to update on all nodes .
On 28 June 2016 at 14:51, Tyler Hobbs <ty...@datastax.com <javascript:_e(%7B%7D,'cvml','ty...@datastax.com');>> wrote: > First, make sure that you call nodetool flush after modifying the system > table. That's probably why it's not surviving the restart. > > Second, I believe you will have to do this across all nodes and restart > them at the same time. Otherwise, cluster name mismatches will prevent the > nodes from communicating with each other. > > On Fri, Jun 24, 2016 at 3:51 PM, Paul Fife <paulf...@gmail.com > <javascript:_e(%7B%7D,'cvml','paulf...@gmail.com');>> wrote: > >> I am following the instructions here to attempt to change the name of a >> cluster: https://wiki.apache.org/cassandra/FAQ#clustername_mismatch >> or at least the more up to date advice: >> http://stackoverflow.com/questions/22006887/cassandra-saved-cluster-name-test-cluster-configured-name >> >> I am able to query the system.local to verify the clusterName is >> modified, but when I restart Cassandra it fails, and the value is back at >> the original cluster name. Is this still possible, or are there changes >> preventing this from working anymore? >> >> I have attempted this several times and it did actually work the first >> time, but when I moved around to the other nodes it no longer worked. >> >> Thanks, >> Paul Fife >> >> > > > -- > Tyler Hobbs > DataStax <http://datastax.com/> >
