Return-Path: Delivered-To: apmail-cassandra-user-archive@www.apache.org Received: (qmail 24146 invoked from network); 14 Jul 2010 19:14:01 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 14 Jul 2010 19:14:01 -0000 Received: (qmail 11601 invoked by uid 500); 14 Jul 2010 19:13:59 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 11543 invoked by uid 500); 14 Jul 2010 19:13:59 -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 11535 invoked by uid 99); 14 Jul 2010 19:13:59 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 14 Jul 2010 19:13:59 +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 jbellis@gmail.com designates 209.85.212.172 as permitted sender) Received: from [209.85.212.172] (HELO mail-px0-f172.google.com) (209.85.212.172) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 14 Jul 2010 19:13:52 +0000 Received: by pxi20 with SMTP id 20so144750pxi.31 for ; Wed, 14 Jul 2010 12:13:31 -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=jQ+i6DuD967wcRPWHWJ+UktrZnCACjZg9NwAhNr9VQE=; b=Z3MnxvBnBn/hFYAzLPdh186PXO/ga5i5iXIAWXGYXa5r98f19cTK7buFas7NcSq2az TL2Hht/lhQ9cdRNb33Yc5fOOU59fOcX8ZpwRlOwSX2qhvENI4DzPk3YIcFYBMxWL2k5q A4Z0G2qSyew79lfEwu0QLBHo28YtrPNsd+SVA= 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=KAK/sYFkSAR2vceYjiXQp91WXaAuNNddeQ+5i2M9SrlEXxnxmz/nyNN+uOC7tEfgmI pIAQ0z5zd7oZk+FDkG+PJkMBv+1smh2tLyWY/5QGYD4BaRaOkixrlU5dodffKE0LnSko 8G8sfuk5IacBcuRrmZiAaWxBWWF8XkwmW577I= Received: by 10.142.213.14 with SMTP id l14mr3939786wfg.315.1279134810213; Wed, 14 Jul 2010 12:13:30 -0700 (PDT) MIME-Version: 1.0 Received: by 10.142.103.9 with HTTP; Wed, 14 Jul 2010 12:13:10 -0700 (PDT) In-Reply-To: <1279132996.20148.44.camel@rnwk-dell> References: <1279132996.20148.44.camel@rnwk-dell> From: Jonathan Ellis Date: Wed, 14 Jul 2010 14:13:10 -0500 Message-ID: Subject: Re: node down window 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 On Wed, Jul 14, 2010 at 1:43 PM, B. Todd Burruss wrote: > there is a window of time from when a node goes down and when the rest > of the cluster actually realizes that it is down. > > what happens to writes during this time frame? =A0does hinted handoff > record these writes and then "handoff" when the down node returns? =A0or > does hinted handoff not kick in until the cluster realizes the node is > down? the latter. > ... is the only way these missed writes are repaired is through read > repair and/or manually kicking off "nodetool repair"? yes. --=20 Jonathan Ellis Project Chair, Apache Cassandra co-founder of Riptano, the source for professional Cassandra support http://riptano.com