Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: Apache Wiki <wikidiffs@apache.org>
To: Apache Wiki <wikidiffs@apache.org>
Date: Fri, 17 Sep 2010 00:00:12 -0000
Message-ID: <20100917000012.69960.49645@eosnew.apache.org>
Subject: =?utf-8?q?=5BCassandra_Wiki=5D_Update_of_=22FAQ=22_by_JonHermes?=

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 JonHermes.
http://wiki.apache.org/cassandra/FAQ?action=3Ddiff&rev1=3D83&rev2=3D84

--------------------------------------------------

  Yes, but it will require restarting and running repair manually to change=
 the replica count of existing data.
  =

   * Alter the ReplicationFactor for the desired keyspace(s) in the storage=
 configuration on each node in the cluster.
-  * Restart cassandra on each node in the cluster
+  * Restart cassandra on each node in the cluster.
  =

  If you're reducing the ReplicationFactor:
  =

-  * Run "nodetool cleanup" on the cluster to remove surplus replicated dat=
a.
+  * Run "nodetool cleanup" on the cluster to remove surplus replicated dat=
a. Cleanup runs on a per-node basis.
  =

  If you're increasing the ReplicationFactor:
  =

-  * Run "nodetool repair" to run an anti-entropy repair on the cluster. Th=
is is an intensive process so may result in adverse cluster performance.
+  * Run "nodetool repair" to run an anti-entropy repair on the cluster. Re=
pair runs on a per-node basis. This is an intensive process that will resul=
t in adverse cluster performance. It's highly recommended to do rolling rep=
airs, as an attempt to repair the entire cluster at once will most likely s=
wamp it and may even kill it.
  =

  <<Anchor(large_file_and_blob_storage)>>
 =20