Return-Path: Delivered-To: apmail-cassandra-user-archive@www.apache.org Received: (qmail 58911 invoked from network); 29 Mar 2011 21:21:11 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 29 Mar 2011 21:21:11 -0000 Received: (qmail 8559 invoked by uid 500); 29 Mar 2011 21:21:07 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 8489 invoked by uid 500); 29 Mar 2011 21:21:07 -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 8306 invoked by uid 500); 29 Mar 2011 21:21:07 -0000 Delivered-To: apmail-incubator-cassandra-user@incubator.apache.org Received: (qmail 8267 invoked by uid 99); 29 Mar 2011 21:21:07 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 29 Mar 2011 21:21:07 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [209.85.160.175] (HELO mail-gy0-f175.google.com) (209.85.160.175) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 29 Mar 2011 21:20:59 +0000 Received: by gyf1 with SMTP id 1so270560gyf.6 for ; Tue, 29 Mar 2011 14:20:37 -0700 (PDT) MIME-Version: 1.0 Received: by 10.150.162.4 with SMTP id k4mr680580ybe.125.1301433637683; Tue, 29 Mar 2011 14:20:37 -0700 (PDT) Sender: scode@scode.org Received: by 10.150.147.9 with HTTP; Tue, 29 Mar 2011 14:20:37 -0700 (PDT) X-Originating-IP: [213.114.157.84] In-Reply-To: <1301428784487-6220683.post@n2.nabble.com> References: <1301417775944-6220005.post@n2.nabble.com> <1301420212192-6220171.post@n2.nabble.com> <1301421070734-6220228.post@n2.nabble.com> <1301424132945-6220423.post@n2.nabble.com> <1301428784487-6220683.post@n2.nabble.com> Date: Tue, 29 Mar 2011 23:20:37 +0200 X-Google-Sender-Auth: y-gn2nY_Z0D-N2OAttaliq9acRY Message-ID: Subject: Re: How to determine if repair need to be run From: Peter Schuller To: user@cassandra.apache.org Cc: mcasandra , cassandra-user@incubator.apache.org Content-Type: text/plain; charset=UTF-8 > Looks like you didn't get to see my updated post :) This is the scenario I > was referring to: I don't see what's different. If you write a QUORUM and read at QUORUM, your read is guaranteed to see a previous write, period. If that cannot be satisfied, the read will fail due to not being able to satisfy QUORUM. What is the actual sequence of events that you are worried about? B going down is not a problem. *By definition*, any two quorum of nodes are overlapping by at least one node. Either a read succeeds and you see the data, or there is no quorum and the read fails. -- / Peter Schuller