Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id CD49E200BC1 for ; Wed, 16 Nov 2016 16:48:35 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id CBD2C160B08; Wed, 16 Nov 2016 15:48:35 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id ED1FC160B02 for ; Wed, 16 Nov 2016 16:48:34 +0100 (CET) Received: (qmail 68062 invoked by uid 500); 16 Nov 2016 15:48:33 -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 68052 invoked by uid 99); 16 Nov 2016 15:48:33 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 16 Nov 2016 15:48:33 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id E2EC5C3191 for ; Wed, 16 Nov 2016 15:48:32 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.398 X-Spam-Level: ** X-Spam-Status: No, score=2.398 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=2, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_SORBS_SPAM=0.5, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd1-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id Gd23SlyV3k_6 for ; Wed, 16 Nov 2016 15:48:30 +0000 (UTC) Received: from mail-ua0-f175.google.com (mail-ua0-f175.google.com [209.85.217.175]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTPS id 3DD825FAE7 for ; Wed, 16 Nov 2016 15:48:30 +0000 (UTC) Received: by mail-ua0-f175.google.com with SMTP id 51so117397956uai.1 for ; Wed, 16 Nov 2016 07:48:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=09ZLkAuf0dgshI0D0ThmxfvkjkbirTWiNZyUqVE0tUM=; b=T/OAW4qmsyNfGy18eX2OdPV35dsZO2YR9xKK3lGbVqTh0odI5EnKKCqB7AY79V+oEf WnUgaQc4B9pNhP+ieculQ4M3IpoY+gDNeEwfIHj4ozsThLGBVf3LWlQ9a2GLf+590Z+z ghxst66dUwninscQR8iXnBBqR0PMW6Bc+vWZdZ9lXzgrJ9v0NdYQy8FTz0NYR2doga8i yHOGVX9++NdD/TPW7riNMn060iXKfdCFR1QDqxr8w0W5/wRrfJQ6NRGpG86qkkvbiPQ0 usxZPg4Waa0OA4VPDCDbeN3YnboSWRM5fPt6jqRUuxC+/kAHwUr6yuW/A8pPG7FzNRZ9 cVwQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=09ZLkAuf0dgshI0D0ThmxfvkjkbirTWiNZyUqVE0tUM=; b=B6XfZ7jLKnwTlJ2pPYslqR+s1mQxfe82YyAWGyeZG9Le7dNi0MSBnJlZgf51XIIReo 90AuNwDmKoVDdGoawVChiKsT9r1A635ViZJyAn0GsG1ea7c3tjng4U6MztNbciHd/fTu zd8RyAoj5BRFGROrp0BQpp2egPPNSqVfBFd6ozZFXKzb2iP0s8hdekSTKAdAdfkDLbuK FolXgIYbLjtwJA2/C/Xd6xz5KMxWmGOZudw4Eq8iZtAQXyZzq7l+whfJWcRiNnuBRYQr OyCBfIGxNnW5oDlSAUjYcWf0Tmp0/4yT9hyn7TDKStFoHyKEI8Q3q7VRB5bUmuihrIIO AF9g== X-Gm-Message-State: ABUngvcYXv3lppum9qPciuaUfMWn2L3u0TmNf+rP1wmTRkQo5J6bIIN3lCpzSsNUcHb3YKwkZ5pNMzwv6n6NXg== X-Received: by 10.176.3.137 with SMTP id 9mr1730506uau.120.1479311301883; Wed, 16 Nov 2016 07:48:21 -0800 (PST) MIME-Version: 1.0 Received: by 10.159.48.141 with HTTP; Wed, 16 Nov 2016 07:48:01 -0800 (PST) In-Reply-To: <236493199.3304114.1479142356443@mail.yahoo.com> References: <236493199.3304114.1479142356443.ref@mail.yahoo.com> <236493199.3304114.1479142356443@mail.yahoo.com> From: Alain RODRIGUEZ Date: Wed, 16 Nov 2016 16:48:01 +0100 Message-ID: Subject: Re: Tomstones impact on repairs both anti-entropy and read repair To: user@cassandra.apache.org, K F Content-Type: multipart/alternative; boundary=94eb2c056316a93da505416d00a9 archived-at: Wed, 16 Nov 2016 15:48:36 -0000 --94eb2c056316a93da505416d00a9 Content-Type: text/plain; charset=UTF-8 Hi, > My question to the community is will tombstone cause issues in data > consistency across the DCs. It might, if your repairs are not succeeding for some reason or not running fully (all the token ranges) within gc_grace_second (parameter at the table level) I wrote a blog post and talked about that at the summit, see: http://thelastpickle.com/blog/2016/07/27/about-deletes-and-tombstones.html https://www.youtube.com/watch?v=lReTEcnzl7Y Let me know if you still have questions after reading / listening to this. C*heers, ----------------------- Alain Rodriguez - @arodream - alain@thelastpickle.com France The Last Pickle - Apache Cassandra Consulting http://www.thelastpickle.com 2016-11-14 17:52 GMT+01:00 K F : > Hi Folks, > > I have a table that has lot of tombstones generated and has caused > inconsistent data across various datacenters. we run anti-entropy repairs > and also have read_repair_chance tuned-up during our non busy hours. But > yet when we try to compare data residing in various replicas across DCs, we > see inconsistency. > > My question to the community is will tombstone cause issues in data > consistency across the DCs. > > Thanks. > --94eb2c056316a93da505416d00a9 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi,
=C2=A0
My question to the community is will t= ombstone cause issues in data consistency across the DCs.

It might, if your repairs are not succeeding for some= reason or not running fully (all the token ranges) within gc_grace_second = (parameter at the table level)

I wrote a blog post= and talked about that at the summit, see:


Let me know if you still have questions after rea= ding / listening to this.

C*heers,
-----------------------
Alain Rodriguez - @arodream - alain@thelastpickle.com
France

The Last Pickle - Apache C= assandra Consulting

2016-11-14 17:52 GMT+01:00 K F <kf200467@yahoo.com>:
Hi Folks,

I = have a table that has lot of tombstones generated and has caused inconsiste= nt data across various datacenters. we run anti-entropy repairs and also ha= ve read_repair_chance tuned-up during our non busy hours. But yet when we t= ry to compare data residing in various replicas across DCs, we see inconsis= tency.

My question to the community is will tombstone cause issues in = data consistency across the DCs.

Thanks.

--94eb2c056316a93da505416d00a9--