[ https://issues.apache.org/jira/browse/CASSANDRA-5997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis resolved CASSANDRA-5997. --------------------------------------- Resolution: Won't Fix > -D option to change cluster name > -------------------------------- > > Key: CASSANDRA-5997 > URL: https://issues.apache.org/jira/browse/CASSANDRA-5997 > Project: Cassandra > Issue Type: Improvement > Reporter: Robert Coli > Priority: Minor > > A steady trickle of users have a need to change the name of their cluster. > Perhaps they accidentally started their cluster with the wrong name and now > want to change it. > http://wiki.apache.org/cassandra/FAQ#clustername_mismatch > Has the old recommendation, which was to edit the cluster name in > LocationInfo and then restart. > http://comments.gmane.org/gmane.comp.db.cassandra.user/29753 > Has the old workaround, which was to remove LocationInfo CF entirely. > As this info now lives in a column called "cluster_name" in a row with key > "local" in a CF called "local" in the keyspace "system", one can no longer > simply nuke LocationInfo. The only workaround remaining is to nuke the entire > system Keyspace and re-coalesce the cluster, and then reload schema. > The community continues to need to perform this operation and we do not want > to tell them to nuke or manually modify the system keyspace (though it seems > they have perms again to modify..). This ticket requests a new startup -D > flag "-Dcassandra.new_cluster_name" which allows one to overwrite this value > at startup time. This means a rolling restart will accomplish the "rename my > cluster" task, with only the cost of split-cluster for the duration. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira