From user-return-34533-apmail-cassandra-user-archive=cassandra.apache.org@cassandra.apache.org Mon Jun 10 13:05:14 2013 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 94B8210736 for ; Mon, 10 Jun 2013 13:05:14 +0000 (UTC) Received: (qmail 39125 invoked by uid 500); 10 Jun 2013 13:05:11 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 39086 invoked by uid 500); 10 Jun 2013 13:05:11 -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 39075 invoked by uid 99); 10 Jun 2013 13:05:08 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 10 Jun 2013 13:05:08 +0000 X-ASF-Spam-Status: No, hits=2.2 required=5.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of post@fantasista.no designates 213.236.237.140 as permitted sender) Received: from [213.236.237.140] (HELO mx1.mailserveren.com) (213.236.237.140) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 10 Jun 2013 13:05:01 +0000 Received: from localhost ([127.0.0.1]) by mx1.mailserveren.com with esmtpa (Exim 4.80.1) (envelope-from ) id 1Um1m2-0002Lu-Nc for user@cassandra.apache.org; Mon, 10 Jun 2013 15:04:38 +0200 Message-Id: From: "Vegard Berget" Reply-To: "Vegard Berget" To: user@cassandra.apache.org X-Mailer: Atmail 6.6.2.11727 X-Originating-IP: 46.19.16.3 Subject: Changing replication factor Date: Mon, 10 Jun 2013 15:04:38 +0200 Content-Type: multipart/alternative; boundary="=_895cedf8e97a001e2d2254c170947e1b" MIME-Version: 1.0 X-Virus-Checked: Checked by ClamAV on apache.org --=_895cedf8e97a001e2d2254c170947e1b Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi,=0AIf one increases the replication factor of a keyspace and then do= a=0Arepair, how will this affect the performance of the affected nodes?= =0ACould we risk the nodes being (more or less) unresponsive while repai= r=0Ais going on? =C2=A0The nodes I am speaking of contains ~100gb of dat= a.=0A=C2=A0Also, some of the keyspaces I am considering increase the=0Ar= eplication factor for contains Counter Column Families (has rf:1).=0A=C2= =A0I think I have read that adding replication to counter cfs will=0Aaff= ect performance negatively, is this correct? =C2=A0=0ACassandra version= is 1.1.7.=0A.vegard, --=_895cedf8e97a001e2d2254c170947e1b Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi,

If one increases the r= eplication factor of a keyspace and then do a repair, how will this affe= ct the performance of the affected nodes? Could we risk the nodes being= (more or less) unresponsive while repair is going on? =C2=A0The nodes I= am speaking of contains ~100gb of data. =C2=A0
Also, some of= the keyspaces I am considering increase the replication factor for cont= ains Counter Column Families (has rf:1). =C2=A0I think I have read that= adding replication to counter cfs will affect performance negatively, i= s this correct? =C2=A0

Cassandra version is 1= 1.7.

.vegard,
--=_895cedf8e97a001e2d2254c170947e1b--