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 31A129EFD for ; Wed, 24 Oct 2012 11:52:26 +0000 (UTC) Received: (qmail 51471 invoked by uid 500); 24 Oct 2012 11:52:23 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 51349 invoked by uid 500); 24 Oct 2012 11:52:23 -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 51320 invoked by uid 99); 24 Oct 2012 11:52:22 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 24 Oct 2012 11:52:22 +0000 X-ASF-Spam-Status: No, hits=-1.0 required=5.0 tests=RCVD_IN_DNSWL_MED,SPF_PASS,URI_HEX X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [192.174.58.133] (HELO XEDGEB.nrel.gov) (192.174.58.133) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 24 Oct 2012 11:52:15 +0000 Received: from XHUBA.nrel.gov (10.20.4.58) by XEDGEB.nrel.gov (192.174.58.133) with Microsoft SMTP Server (TLS) id 8.3.245.1; Wed, 24 Oct 2012 05:51:50 -0600 Received: from MAILBOX2.nrel.gov ([fe80::19a0:6c19:6421:12f]) by XHUBA.nrel.gov ([::1]) with mapi; Wed, 24 Oct 2012 05:51:53 -0600 From: "Hiller, Dean" To: "user@cassandra.apache.org" Date: Wed, 24 Oct 2012 05:51:51 -0600 Subject: Re: What does ReadRepair exactly do? Thread-Topic: What does ReadRepair exactly do? Thread-Index: Ac2x3fUWAYZty4BfTuuIQ4D9NLaVPw== Message-ID: In-Reply-To: <1351040699422-7583355.post@n2.nabble.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.2.4.120824 acceptlanguage: en-US Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Virus-Checked: Checked by ClamAV on apache.org Keep in mind, returning the older version is usually fine. Just imagine if your user clicked write 1 ms before, then the new version might be returned. If he gets the older version and refreshes the page, he gets the newer version. Same with an automated program as well=8A.in general it is okay to get the older or newer value. If you are reading 2 rows however instead of one, that may change. Dean On 10/23/12 7:04 PM, "shankarpnsn" wrote: >manuzhang wrote >> why repair again? We block until the consistency constraint is met. Then >> the latest version is returned and repair is done asynchronously if any >> mismatch. We may retry read if fewer columns than required are returned. > >Just to make sure I understand you correct, considering the case when a >read >repair is in flight and a subsequent write affects one or more of the >replicas that was scheduled to received the repair mutations. In this >case, >are you saying that we return the older version to the user rather than >the >latest version that was effected by the write ? > > > >-- >View this message in context: >http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/What-does >-ReadRepair-exactly-do-tp7583261p7583355.html >Sent from the cassandra-user@incubator.apache.org mailing list archive at >Nabble.com.