Indeed when you want to flush the system keyspace you need to specify it. The
flush without argument filters out the system keyspace. This behavior is still
the same in the trunk. If you dig into the sources, look at
"nodeProbe.getNonSystemKeyspaces()" when "cmdArgs" is empty:-
https://github.c
Thanks Dominik - I was doing a nodetool flush like the instructions said,
but it wasn't actually flushing the system keyspace. Using nodetool flush
system made it work as expected!
Thanks,
Paul Fife
On Wed, Jun 29, 2016 at 7:37 AM, Dominik Keil
wrote:
> Also you might want to explicitly do "nod
Also you might want to explicitly do "nodetool flush system". I've
recently done this in C* 2.2.6 and just "nodetool flush" would not have
flushed the system keyspace, leading to the change in cluster name not
being persisted across restarts.
Cheers
Am 29.06.2016 um 03:36 schrieb Surbhi Gupta
system.local uses local strategy . You need to update on all nodes .
On 28 June 2016 at 14:51, Tyler Hobbs > 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 t
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 commun
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 que
