Dear Wiki user, You have subscribed to a wiki page or wiki category on "Cassandra Wiki" for change notification.
The "FAQ" page has been changed by JoaquinCasares: http://wiki.apache.org/cassandra/FAQ?action=diff&rev1=144&rev2=145 <<Anchor(clustername_mismatch)>> == Cassandra says "ClusterName mismatch: oldClusterName != newClusterName" and refuses to start == - To prevent operator errors, Cassandra stores the name of the cluster in its system table. If you need to rename a cluster for some reason, it is safe to remove system/LocationInfo* after forcing a compaction on all !ColumnFamilies (with the old cluster name) if you've specified the node's token in the config file, or if you don't care about preserving the node's token (for instance in single node clusters.) + To prevent operator errors, Cassandra stores the name of the cluster in its system table. If you need to rename a cluster for some reason, you can: + + Perform these steps on each node: + 1. Start the `cassandra-cli` connected locally to this node. + 1. Run the following: + a. use system; + a. set LocationInfo[utf8('L')][utf8('ClusterName')]=utf8('<new cluster name>'); + a. exit; + 1. Run `nodetool flush` on this node. + 1. Update the cassandra.yaml file for the cluster_name as the same as 2b). + 1. Restart the node. + + Once all nodes have been had this operation performed and restarted, `nodetool ring` should show all nodes as UP. <<Anchor(batch_mutate_atomic)>>
