Return-Path: Delivered-To: apmail-cassandra-user-archive@www.apache.org Received: (qmail 47834 invoked from network); 18 Aug 2010 14:30:57 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 18 Aug 2010 14:30:57 -0000 Received: (qmail 1863 invoked by uid 500); 18 Aug 2010 14:30:56 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 1718 invoked by uid 500); 18 Aug 2010 14:30:53 -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 1710 invoked by uid 99); 18 Aug 2010 14:30:53 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 18 Aug 2010 14:30:53 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of raj.cassandra@gmail.com designates 209.85.213.66 as permitted sender) Received: from [209.85.213.66] (HELO mail-yw0-f66.google.com) (209.85.213.66) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 18 Aug 2010 14:30:48 +0000 Received: by ywg4 with SMTP id 4so25518ywg.1 for ; Wed, 18 Aug 2010 07:30:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:date:message-id :subject:from:to:content-type; bh=45qIGALIj8G5wEMj334tUcPV4iaCfpMibIvFq6Picjo=; b=jlIzVq2mtaLPJt4UH5bbAV/qaM/VMseEvRvhOBa4MvTG8AXjFA6uzuFPF43pAPpZgT 1Z7ndCSyurmx26JOaOFnXQZYzE/KOhBk8i8kRw2GtM4iZuitsTjqIQMqJeQvvom+CXJB q0Cz21A53dL8Rd4e3EinEkFuVI0RdyZKuNZbA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=IZ29RJW5l9qsojidvnLpGFKzMpM4c5g3i6gZlepe53f838yvKsgIvQma6rwaPk4U7m OZOuSYYpR4nT2szgVvqeteAYWTBMGt43eVK7vegpsa1k1Tm1ewc8epNpFdoK5+7IxBw7 6J43GPILUrXyRW0gi6ZF26xod0V41S0IoYsP4= MIME-Version: 1.0 Received: by 10.151.145.6 with SMTP id x6mr346161ybn.277.1282141828179; Wed, 18 Aug 2010 07:30:28 -0700 (PDT) Received: by 10.231.207.73 with HTTP; Wed, 18 Aug 2010 07:30:28 -0700 (PDT) Date: Wed, 18 Aug 2010 10:30:28 -0400 Message-ID: Subject: RE: data deleted came back after 9 days. From: Raj N To: user@cassandra.apache.org Content-Type: multipart/alternative; boundary=0015174c44703868eb048e19e87a --0015174c44703868eb048e19e87a Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Guys, Correct me if I am wrong. The whole problem is because a node missed an update when it was down. Shouldn=92t HintedHandoff take care of this case? Thanks -Raj -----Original Message----- From: Jonathan Ellis [mailto:jbellis@gmail.com] Sent: Wednesday, August 18, 2010 9:22 AM To: user@cassandra.apache.org Subject: Re: data deleted came back after 9 days. Actually, tombstones are read repaired too -- as long as they are not expired. But nodetool repair is much less error-prone than relying on RR and your memory of what deletes you issued. Either way, you'd need to increase GCGraceSeconds first to make the tombstones un-expired first. On Wed, Aug 18, 2010 at 12:43 AM, Benjamin Black wrote: > On Tue, Aug 17, 2010 at 7:49 PM, Zhong Li wrote: >> Those data were inserted one node, then deleted on a remote node in >> less than 2 seconds. So it is very possible some node lost tombstone >> when connection lost. >> My question, is a ConstencyLevel.ALL read can retrieve lost tombstone >> back instead of repair? >> > > No. Read repair does not replay operations. You must run nodetool repair. > > > b > -- Jonathan Ellis Project Chair, Apache Cassandra co-founder of Riptano, the source for professional Cassandra support http://riptano.com --0015174c44703868eb048e19e87a Content-Type: text/html; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Guys,
=A0=A0=A0 Correct me if I am wrong. The whole problem is because a= node missed an update when it was down. Shouldn=92t HintedHandoff take car= e of this case?

Thanks
-Raj

-----Original Message-----
= From: Jonathan Ellis [mailto:jbellis@g= mail.com]
Sent: Wednesday, August 18, 2010 9:22 AM
To: user@cassandra.apache.org
Subject: Re: data delete= d came back after 9 days.

Actually, tombstones are read repaired too= -- as long as they are not expired.=A0 But nodetool repair is much less er= ror-prone than relying on RR and your memory of what deletes you issued.
Either way, you'd need to increase GCGraceSeconds first to make the= tombstones un-expired first.

On Wed, Aug 18, 2010 at 12:43 AM, Benj= amin Black <b@b3k.us> wrote:
> = On Tue, Aug 17, 2010 at 7:49 PM, Zhong Li <zli@voxeo.com> wrote:
>> Those data were inserted one node, then deleted on a remote node i= n
>> less than 2 seconds. So it is very possible some node lost t= ombstone
>> when connection lost.
>> My question, is a C= onstencyLevel.ALL read can retrieve=A0lost=A0tombstone
>> back instead of repair?
>>
>
> No. =A0Read re= pair does not replay operations. =A0You must run nodetool repair.
>>
> b
>



--
Jonathan Ellis
Project Cha= ir, Apache Cassandra
co-founder of Riptano, the source for professional Cassandra support http://riptano.com
--0015174c44703868eb048e19e87a--