Return-Path: Delivered-To: apmail-cassandra-user-archive@www.apache.org Received: (qmail 5974 invoked from network); 2 Nov 2010 13:33:14 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 2 Nov 2010 13:33:14 -0000 Received: (qmail 59374 invoked by uid 500); 2 Nov 2010 13:33:43 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 58788 invoked by uid 500); 2 Nov 2010 13:33:38 -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 58780 invoked by uid 99); 2 Nov 2010 13:33:37 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 02 Nov 2010 13:33:37 +0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of joe.m.alex@gmail.com designates 209.85.213.44 as permitted sender) Received: from [209.85.213.44] (HELO mail-yw0-f44.google.com) (209.85.213.44) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 02 Nov 2010 13:33:30 +0000 Received: by ywp6 with SMTP id 6so4409217ywp.31 for ; Tue, 02 Nov 2010 06:33:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:mime-version:received:in-reply-to :references:from:date:message-id:subject:to:content-type :content-transfer-encoding; bh=PkinEy0K4JkeNCDCFFE5Evu82yuJ5qLDrmjAFIWtkHs=; b=mzmXF6Om8B14ch0QgVF2bh1jctOfoOwONadoOmEfGvKTZLeOgLZdepildB33BLgcWD NWUM1BJU6t03tKM1srG4YnixbnVMVY8ZkJQF/HQ4OCRsdtpGoVaWVCKKaHdIimMi8J4I DDq44uEkwNfaUtN0j4fWybrNJ6rSOlDiLo9DM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type:content-transfer-encoding; b=ZLQV7bTBG6hsr1R/FMA+iyg5CrXCujnkHJg84AMY5Psl9OtBOGbH3VyzakuNvCtGy4 WhRf7Iz5Bib49xXDelfd7IFcmlbn6WBq2yqU1M2yeuGvdUiCc+swpen8uRGgtY8VLVtz dAO4qT6PjIX58RFGcKjpqnfk98WRlHmzSDwKE= Received: by 10.42.210.143 with SMTP id gk15mr12043893icb.509.1288704789051; Tue, 02 Nov 2010 06:33:09 -0700 (PDT) MIME-Version: 1.0 Received: by 10.220.177.5 with HTTP; Tue, 2 Nov 2010 06:32:46 -0700 (PDT) In-Reply-To: References: From: Joe Alex Date: Tue, 2 Nov 2010 09:32:46 -0400 Message-ID: Subject: Re: Question on Hinted Handoff To: user@cassandra.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org Thanks, that clarifies why HH did not work, So have to use .7. Is there .6.7 ? I am using .6.6 now. I did see the log entry in Node 4, adding a Hint for Node 2 and when Node 2 came up noticed a log entry in Node 4 that 1 row Handed Off - so I thought it was working. About RR - a read in Node 1 or Node 2 indicated a RR (see log entry above) was happening. But dont think that ever happened. Those entries keep repeating every time a read in Node 1 and 2 and kept giving old data. AES assuming Anti-Entropy - Tried nodetool repair, this also did not fix the issue. The only time I saw it being fixed was a read to Node 3 or Node 4 (mostly Node 3 which acted as responsible when Node 2 was down) and then 2nd reads to Node 2 started showing the latest data. Do you think RR and AES should have definitely worked ? On Tue, Nov 2, 2010 at 1:01 AM, Brandon Williams wrote: > On Mon, Nov 1, 2010 at 8:28 PM, Joe Alex wrote: >> >> My expectation was even though Node 2 was down key written to Node 3 >> or 4 should be updated in Node 2 using Hint and the subsequent reads >> to Node 1 or Node 2 itself should have got the latest value > > Your expectation is correct, unfortunately I broke HH in 0.6.5 with a bad > backport and it affects > 0.6.6:=A0https://issues.apache.org/jira/browse/CASSANDRA-1656 > But, that is why we have Read Repair and AES. =A0It's worth noting that H= H is > best effort anyway, if Node 2 was down but the failure detector hadn't > noticed yet, no hint would be created and you'd have the same behavior. > -Brandon