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 9082B3E36 for ; Mon, 2 May 2011 18:09:56 +0000 (UTC) Received: (qmail 4468 invoked by uid 500); 2 May 2011 18:09:54 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 4443 invoked by uid 500); 2 May 2011 18:09:54 -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 4435 invoked by uid 99); 2 May 2011 18:09:54 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 02 May 2011 18:09:54 +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 robertj@promedicalinc.com designates 97.66.157.146 as permitted sender) Received: from [97.66.157.146] (HELO zixvpm01.promedicalinc.com) (97.66.157.146) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 02 May 2011 18:09:46 +0000 Received: from zixvpm01.promedicalinc.com (ZixVPM [127.0.0.1]) by Outbound.promedicalinc.com (Proprietary) with ESMTP id 34C1519D80B8 for ; Mon, 2 May 2011 13:28:36 -0400 (EDT) Received: from mail.promedicalinc.com (mail.promedicalinc.com [97.66.157.136]) by zixvpm01.promedicalinc.com (Proprietary) with ESMTP id D5FDD19D80B2 for ; Mon, 2 May 2011 13:28:34 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by mail.promedicalinc.com (Postfix) with ESMTP id 1C081E52006 for ; Mon, 2 May 2011 14:10:01 -0400 (EDT) X-Virus-Scanned: amavisd-new at promedicalinc.com Received: from mail.promedicalinc.com ([127.0.0.1]) by localhost (mail.promedicalinc.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jEZaKe1qcL5f for ; Mon, 2 May 2011 14:09:53 -0400 (EDT) Received: from mail.promedicalinc.com (mail.promedicalinc.com [97.66.157.136]) by mail.promedicalinc.com (Postfix) with ESMTP id ACA23E52002 for ; Mon, 2 May 2011 14:09:53 -0400 (EDT) Date: Mon, 2 May 2011 14:09:53 -0400 (EDT) From: Robert Jackson To: user@cassandra.apache.org Message-ID: <1286734955.74355.1304359793510.JavaMail.root@mail> In-Reply-To: Subject: Re: Specifying exact nodes for Consistency Levels MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_74354_937164979.1304359793510" X-Originating-IP: [192.168.100.110] X-Mailer: Zimbra 6.0.8_GA_2661 (ZimbraWebClient - FF3.0 (Mac)/6.0.8_GA_2661) X-Virus-Checked: Checked by ClamAV on apache.org ------=_Part_74354_937164979.1304359793510 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit The only way I can think of would be to use NetworkTopologyStrategy and PropertyFileSnitch to define two data centers. Set node1-node3 in DC1 then set node4 in DC2. Then set the strategy_options=[{DC1:3, DC2:1}] for that keyspace. This would make your cluster conceptually similar to a split datacenter as described in the Brisk white paper. References: http://www.datastax.com/docs/0.7/operations/datacenter http://www.datastax.com/wp-content/uploads/2011/03/WP-Brisk.pdf Robert Jackson ----- Original Message ----- From: "A J" To: user@cassandra.apache.org Sent: Monday, May 2, 2011 1:26:31 PM Subject: Specifying exact nodes for Consistency Levels Is it possible in some way to specify what specific nodes I want to include (or exclude) from the Consistency Level fulfillment ? Example, I have a cluster of 4 nodes (n1,n2,n3 and n4) and set N=4. I want to set W=3 and want to ensure that it is n1,n2 and n3 only that are used to satisfy w=3 (i.e. n4 is excluded for w=3 calculation). Thanks. ------=_Part_74354_937164979.1304359793510 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable <= div style=3D'font-family: Times New Roman; font-size: 12pt; color: #000000'= >The only way I can think of would be to use NetworkTopologySt= rategy and PropertyFileSnitch to define two data centers.  Set node1-n= ode3 in DC1 then set node4 in DC2.  Then set the strategy_options=3D[{= DC1:3, DC2:1}] for that keyspace.

This would make your cluster conce= ptually similar to a split datacenter as described in the Brisk white paper= .

References:

http://www.datastax.com/docs/0.7/operations/da= tacenter
http://www.datastax.com/wp-content/uploads/2011/03/WP-Brisk.pdf=

Robert Jackson


From: "A J" <= ;s5alye@gmail.com>
To: user@cassandra.apache.org
Sent: <= /b>Monday, May 2, 2011 1:26:31 PM
Subject: Specifying exact nodes= for Consistency Levels

Is it possible in some way to specify what s= pecific nodes I want to
include (or exclude) from the Consistency Level = fulfillment ?
Example, I have a cluster of 4 nodes (n1,n2,n3 and n4) and= set N=3D4. I
want to set W=3D3 and want to ensure that it is n1,n2 and = n3 only that
are used to satisfy w=3D3 (i.e. n4 is excluded for w=3D3 ca= lculation).

Thanks.
------=_Part_74354_937164979.1304359793510--