Return-Path: X-Original-To: apmail-cassandra-user-archive@www.apache.org Delivered-To: apmail-cassandra-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 70AED776B for ; Mon, 5 Dec 2011 17:11:16 +0000 (UTC) Received: (qmail 60304 invoked by uid 500); 5 Dec 2011 17:11:14 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 60281 invoked by uid 500); 5 Dec 2011 17:11:14 -0000 Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@cassandra.apache.org Delivered-To: mailing list user@cassandra.apache.org Received: (qmail 60273 invoked by uid 99); 5 Dec 2011 17:11:14 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 05 Dec 2011 17:11:14 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of arodrime@gmail.com designates 209.85.215.172 as permitted sender) Received: from [209.85.215.172] (HELO mail-ey0-f172.google.com) (209.85.215.172) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 05 Dec 2011 17:11:07 +0000 Received: by eaak10 with SMTP id k10so1467012eaa.31 for ; Mon, 05 Dec 2011 09:10:47 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=40Idw9fIo43LudQteTcFjasTypRVfhb7F74jInru5OI=; b=RQdKIXi2tTU71kQWYfXd8ACbmCeWlE+NQrhaMvt637I4+BjImCOixjxqi66JtS7mua TscVT+gjIUjo0s244M2KsDQ2GcYEAeymVkmm5FWBMENQOHZvmJINqMdQq5/r7DCzEewm NXOKWj9rHNxfthGjZcL3RdKoy+Fi3zse0tjLE= Received: by 10.213.17.131 with SMTP id s3mr1111290eba.129.1323105046628; Mon, 05 Dec 2011 09:10:46 -0800 (PST) MIME-Version: 1.0 Received: by 10.213.113.200 with HTTP; Mon, 5 Dec 2011 09:10:25 -0800 (PST) In-Reply-To: References: From: Alain RODRIGUEZ Date: Mon, 5 Dec 2011 18:10:25 +0100 Message-ID: Subject: Re: Increase replication factor To: user@cassandra.apache.org Content-Type: multipart/alternative; boundary=0015174be1264e0bd004b35b6606 X-Virus-Checked: Checked by ClamAV on apache.org --0015174be1264e0bd004b35b6606 Content-Type: text/plain; charset=ISO-8859-1 http://www.datastax.com/docs/1.0/operations/cluster_management#changing-the-replication-factor It looks like a nodetool repair is needed after increasing your RF. I guess that a cleanup has to be performed after decreasing the RF to remove useless replica. Alain 2011/12/5 A J > If I update a keyspace to increase the replication factor; what > happens to existing data for that keyspace ? Does the existing data > get automatically increase its replication ? Or only on a RR or node > repair does the existing data increase its replication factor ? > > Thanks. > --0015174be1264e0bd004b35b6606 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable http://www.datastax.com/docs/1.0/operations= /cluster_management#changing-the-replication-factor

It looks lik= e a nodetool repair is needed after increasing your RF. I guess that a clea= nup has to be performed after decreasing the RF to remove useless replica.<= br>
Alain

2011/12/5 A J <s5alye@gmail.com>
If I update a keyspace to increase the replication factor; what
happens to existing data for that keyspace ? Does the existing data
get automatically increase its replication ? Or only on a RR or node
repair does the existing data increase its replication factor ?

Thanks.

--0015174be1264e0bd004b35b6606--