cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Cassandra Wiki] Trivial Update of "FAQ" by jeremyhanna
Date Wed, 29 Oct 2014 21:18:50 GMT
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 jeremyhanna:
https://wiki.apache.org/cassandra/FAQ?action=diff&rev1=168&rev2=169

Comment:
De-linking some capitalized words

  == Can I change the ReplicationFactor on a live cluster? ==
  Yes, but it will require running repair to change the replica count of existing data.
  
-  * Alter the ReplicationFactor for the desired keyspace(s) using cassandra-cli.
+  * Alter the !ReplicationFactor for the desired keyspace(s) using cassandra-cli.
  
- If you're reducing the ReplicationFactor:
+ If you're reducing the !ReplicationFactor:
  
   * Run "nodetool cleanup" on the cluster to remove surplus replicated data. Cleanup runs
on a per-node basis.
  
- If you're increasing the ReplicationFactor:
+ If you're increasing the !ReplicationFactor:
  
   * Run "nodetool repair" to run an anti-entropy repair on the cluster. Repair runs on a
per-replica set basis. This is an intensive process that may result in adverse cluster performance.
It's highly recommended to do rolling repairs, as an attempt to repair the entire cluster
at once will most likely swamp it.
  
@@ -238, +238 @@

   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. 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).
@@ -321, +321 @@

   * The replication factor (decides ''how many'' nodes are in the replica set for a given
row)
   * The replication strategy (decides ''which'' nodes are part of said replica set)
  
- In the case of the SimpleStrategy, replicas are placed on succeeding nodes in the ring.
The first node is determined by the partitioner and the row key, and the remainder are placed
on succeeding node. In the case of NetworkTopologyStrategy placement is affected by data-center
and rack awareness, and the placement will depend on how nodes in different racks or data
centers are placed in the ring.
+ In the case of the !SimpleStrategy, replicas are placed on succeeding nodes in the ring.
The first node is determined by the partitioner and the row key, and the remainder are placed
on succeeding node. In the case of !NetworkTopologyStrategy placement is affected by data-center
and rack awareness, and the placement will depend on how nodes in different racks or data
centers are placed in the ring.
  
  It is important to understand that Cassandra ''does not'' alter the replica set for a given
row key based on changing characteristics like current load, which nodes are up or down, or
which node your client happens to talk to.
  
@@ -442, +442 @@

  
  <<Anchor(opp)>>
  == Why should I avoid order-preserving partitioners? ==
- See [Partitioners].
+ See Partitioners.
  
  <<Anchor(clocktie)>>
  == What happens if two updates are made with the same timestamp? ==

Mime
View raw message