Return-Path: Delivered-To: apmail-cassandra-user-archive@www.apache.org Received: (qmail 70010 invoked from network); 24 Feb 2011 18:29:54 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 24 Feb 2011 18:29:54 -0000 Received: (qmail 16144 invoked by uid 500); 24 Feb 2011 18:29:52 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 16088 invoked by uid 500); 24 Feb 2011 18:29:50 -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 16080 invoked by uid 500); 24 Feb 2011 18:29:49 -0000 Delivered-To: apmail-incubator-cassandra-user@incubator.apache.org Received: (qmail 16077 invoked by uid 99); 24 Feb 2011 18:29:49 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 24 Feb 2011 18:29:49 +0000 X-ASF-Spam-Status: No, hits=2.0 required=5.0 tests=FREEMAIL_FROM,SPF_NEUTRAL,T_TO_NO_BRKTS_FREEMAIL,URI_HEX X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: 216.139.236.26 is neither permitted nor denied by domain of mohitanchlia@gmail.com) Received: from [216.139.236.26] (HELO sam.nabble.com) (216.139.236.26) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 24 Feb 2011 18:29:44 +0000 Received: from jim.nabble.com ([192.168.236.80]) by sam.nabble.com with esmtp (Exim 4.69) (envelope-from ) id 1PsfwK-0001qk-1j for cassandra-user@incubator.apache.org; Thu, 24 Feb 2011 10:29:24 -0800 Date: Thu, 24 Feb 2011 10:29:24 -0800 (PST) From: mcasandra To: cassandra-user@incubator.apache.org Message-ID: <1298572164044-6061399.post@n2.nabble.com> In-Reply-To: <7037359007330560243@unknownmsgid> References: <9f715825-f9bd-6734-fe87-9494463f27c0@me.com> <1298051603878-6040893.post@n2.nabble.com> <1298254421.8166.29.camel@oxygen> <1298313500550-6049678.post@n2.nabble.com> <1298508175769-6058576.post@n2.nabble.com> <7037359007330560243@unknownmsgid> Subject: Re: Understand eventually consistent MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Javier Canillas wrote: > > Instead, when you execute the same OP using CL QUORUM, then it means > RF /2+1, it will try to write on the coordinator node and replica. > Considering only 1 replica is down, the OP will success too. > I am assuming even read will succeed when CL QUORUM and RF=3 and 1 node is down. Javier Canillas wrote: > > Now consider same OP but with CL ALL, it will fail since it cant > assure that coordinador and both replicas are updated. > Can you please explain this little more? I thought CL ALL will fail because it needs all the nodes to be up. http://wiki.apache.org/cassandra/API -- View this message in context: http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/Understand-eventually-consistent-tp6038330p6061399.html Sent from the cassandra-user@incubator.apache.org mailing list archive at Nabble.com.