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 50FBA7962 for ; Tue, 23 Aug 2011 17:06:44 +0000 (UTC) Received: (qmail 57436 invoked by uid 500); 23 Aug 2011 17:06:42 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 57366 invoked by uid 500); 23 Aug 2011 17:06:41 -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 57357 invoked by uid 99); 23 Aug 2011 17:06:41 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 23 Aug 2011 17:06:41 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of edlinuxguru@gmail.com designates 74.125.83.44 as permitted sender) Received: from [74.125.83.44] (HELO mail-gw0-f44.google.com) (74.125.83.44) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 23 Aug 2011 17:06:34 +0000 Received: by gwb20 with SMTP id 20so295357gwb.31 for ; Tue, 23 Aug 2011 10:06:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=rdLl+h6Z8nplQ6pxgh1eYwVuIJ8OlPWLCv35FUkUGws=; b=ZH8dn3S0rvj0QKxfJ3dt1CB5eeKD9yM1ppdRJsREyblIBlswG5rkA1TewHgWhjzKfH ukvj1QlfzjxYQbIcWzohrvyZZG8Pffc6+rrxdQbktBIX4TEsnmDRiLkfMC+vPvM8A107 ziKTW8OpOGwJD1kE6/cIzO7lsL4eyMtZr3ZTE= MIME-Version: 1.0 Received: by 10.42.161.135 with SMTP id t7mr3723833icx.413.1314119173350; Tue, 23 Aug 2011 10:06:13 -0700 (PDT) Received: by 10.42.74.193 with HTTP; Tue, 23 Aug 2011 10:06:13 -0700 (PDT) In-Reply-To: References: Date: Tue, 23 Aug 2011 13:06:13 -0400 Message-ID: Subject: Re: how to know if nodetool cleanup is safe? From: Edward Capriolo To: user@cassandra.apache.org Content-Type: multipart/alternative; boundary=90e6ba1f000685248b04ab2f3688 X-Virus-Checked: Checked by ClamAV on apache.org --90e6ba1f000685248b04ab2f3688 Content-Type: text/plain; charset=ISO-8859-1 On Tue, Aug 23, 2011 at 11:56 AM, Sam Overton wrote: > On 21 August 2011 12:34, Yan Chunlu wrote: > >> since "nodetool cleanup" could remove hinted handoff, will it cause the >> data loss? > > > Hi Yan, > > Hints are not guaranteed to be delivered and "nodetool cleanup" is one of > the reasons for that. This will only cause data-loss if you are writing at > CL.ANY where a hint counts as a write. If you are writing at CL.ONE or above > then at least one replica must receive the data for the write to succeed, so > losing hints will not cause data-loss. > > If a hint is not delivered then the replica to which it was intended will > become consistent after a read-repair, or after manual anti-entropy repair. > > Sam > > -- > Sam Overton > Acunu | http://www.acunu.com | @acunu > If you run nodetool tpstats on each node in your cluster and ensure none of them have an active or pending threads in the Hinted stage no hints are currently being delivered. But as pointed out above Hinted Handoff is a best effort system. --90e6ba1f000685248b04ab2f3688 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
On Tue, Aug 23, 2011 at 11:56 AM, Sam Overto= n <soverton@acun= u.com> wrote:
On 21 August 2011 12:34, Yan Chunlu <spring= rider@gmail.com> wrote:
since "nodetool cleanup" could remove hinted handoff, =A0will it = cause the data loss?

Hi Yan,

Hints are not = guaranteed to be delivered and "nodetool cleanup" is one of the r= easons for that. This will only cause data-loss if you are writing at CL.AN= Y where a hint counts as a write. If you are writing at CL.ONE or above the= n at least one replica must receive the data for the write to succeed, so l= osing hints will not cause data-loss.=A0

If a hint is not delivered then the replica to which it= was intended will become consistent after a read-repair, or after manual a= nti-entropy repair.

Sam

--
Sam Overton
Acunu |=A0http:/= /www.acunu.com=A0| @acunu


If you run nodetool tpstats on each = node in your cluster and ensure none of them have an active or pending thre= ads in the Hinted stage no hints are currently being delivered. But as poin= ted out above Hinted Handoff is a best effort system. =A0
--90e6ba1f000685248b04ab2f3688--