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 NickTelford. The comment on this change is: Added information about changing ReplicationFactor for live clusters. http://wiki.apache.org/cassandra/FAQ?action=diff&rev1=41&rev2=42 -------------------------------------------------- * [[#reads_slower_writes|Why are reads slower than writes?]] * [[#cloned|Why does nodeprobe ring only show one entry, even though my nodes logged that they see each other joining the ring?]] * [[#range_ghosts|Why do deleted keys show up during range scans?]] + * [[#change_replication|Can I change the ReplicationFactor on a live cluster?]] <<Anchor(cant_listen_on_ip_any)>> == Why can't I make Cassandra listen on 0.0.0.0 (all my addresses)? == @@ -186, +187 @@ This is what we used to do with the old get_key_range method, but the performance hit turned out to be unacceptable. + <<Anchor(change_replication)>> + == Can I change the ReplicationFactor on a live cluster? == + Yes, but it will require a little work. + + 1. Alter the ReplicationFactor for the desired keyspace(s) in the storage configuration on each node in the cluster. + 2. Restart cassandra on each node in the cluster + + If you're reducing the ReplicationFactor: + 3. Run "nodetool cleanup" on the cluster to remove surplus replicated data. + + If you're increasing the ReplicationFactor: + 3. Run "nodetool repair" to run an anti-entropy repair on the cluster. This is an intensive process so may result in adverse cluster performance or even down-time while it runs. +
