From cassandra-user-return-1427-apmail-incubator-cassandra-user-archive=incubator.apache.org@incubator.apache.org Thu Nov 19 22:50:08 2009 Return-Path: Delivered-To: apmail-incubator-cassandra-user-archive@minotaur.apache.org Received: (qmail 86394 invoked from network); 19 Nov 2009 22:50:07 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 19 Nov 2009 22:50:07 -0000 Received: (qmail 50632 invoked by uid 500); 19 Nov 2009 22:50:07 -0000 Delivered-To: apmail-incubator-cassandra-user-archive@incubator.apache.org Received: (qmail 50623 invoked by uid 500); 19 Nov 2009 22:50:07 -0000 Mailing-List: contact cassandra-user-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: cassandra-user@incubator.apache.org Delivered-To: mailing list cassandra-user@incubator.apache.org Received: (qmail 50614 invoked by uid 99); 19 Nov 2009 22:50:07 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 19 Nov 2009 22:50:07 +0000 X-ASF-Spam-Status: No, hits=-2.6 required=5.0 tests=BAYES_00 X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of bburruss@real.com designates 207.188.23.4 as permitted sender) Received: from [207.188.23.4] (HELO kal-el.real.com) (207.188.23.4) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 19 Nov 2009 22:50:05 +0000 Received: from [172.21.131.225] ([::ffff:172.21.131.225]) (TLS: TLSv1/SSLv3,256bits,AES256-SHA) by kal-el.real.com with esmtp; Thu, 19 Nov 2009 14:49:44 -0800 id 00080051.4B05CB88.00007BC9 Subject: quorum / hinted handoff From: "B. Todd Burruss" To: cassandra-user@incubator.apache.org Content-Type: text/plain; charset="UTF-8" Date: Thu, 19 Nov 2009 14:49:44 -0800 Message-ID: <1258670984.4757.9.camel@btoddb-laptop> Mime-Version: 1.0 X-Mailer: Evolution 2.28.1 Content-Transfer-Encoding: 7bit I'm doing some testing with build 881977. I have setup a 3 node cluster with ReplicationFactor = 2, reads using ConsistencyLevel.ONE, and writes using ConsistencyLevel.QUORUM. If I take one node out of the cluster, then do some writes I would expect that all the writes would succeed because I still have 2 nodes in the cluster, so I have a quorum. My guess is that since one of the nodes the quorum write "should" use is down, the write fails. Is this the expected behavior? Is hinted handoff in the future? If not, this seems to make quorum kinda useless since some writes will fail if ANY node becomes unavailable for whatever reason. thx!