From user-return-64348-archive-asf-public=cust-asf.ponee.io@cassandra.apache.org Tue Aug 13 16:14:58 2019 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [207.244.88.153]) by mx-eu-01.ponee.io (Postfix) with SMTP id D99251804BB for ; Tue, 13 Aug 2019 18:14:57 +0200 (CEST) Received: (qmail 12362 invoked by uid 500); 13 Aug 2019 16:14:55 -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 12346 invoked by uid 99); 13 Aug 2019 16:14:55 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 13 Aug 2019 16:14:55 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 89E2D180D83 for ; Tue, 13 Aug 2019 16:14:54 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.801 X-Spam-Level: * X-Spam-Status: No, score=1.801 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=2, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=disabled Authentication-Results: spamd3-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=zalando.de Received: from mx1-he-de.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id mxcrK44gaEcO for ; Tue, 13 Aug 2019 16:14:52 +0000 (UTC) Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=2a00:1450:4864:20::12c; helo=mail-lf1-x12c.google.com; envelope-from=oleksandr.shulgin@zalando.de; receiver= Received: from mail-lf1-x12c.google.com (mail-lf1-x12c.google.com [IPv6:2a00:1450:4864:20::12c]) by mx1-he-de.apache.org (ASF Mail Server at mx1-he-de.apache.org) with ESMTPS id 6F3937D3FB for ; Tue, 13 Aug 2019 16:14:51 +0000 (UTC) Received: by mail-lf1-x12c.google.com with SMTP id c19so77177636lfm.10 for ; Tue, 13 Aug 2019 09:14:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=zalando.de; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=vDOTn1DHFWC9cnru/L/wXqu3a7bO9S++Ez2vDwcQwsc=; b=i8U+ctrtuX6TCIOKwaog6+ciEVzmslfQMeU7IATgK90WQ6BA1QWeUr1tYHHykn+5vE o2lcLSVFBCIGT0ZpDUSAprZucHrbEMdGaT/xXTIYcqvzXerL8S9MGGXfAnAoCpMbaRzf hfzUN2JfjNTogynsboA6rtrLcEx3N0RV9C5j4Zh5h/iHfym8ireOabAEKY0M/NYNeaXk rAHFzEZzNkvfW4LR489WgTOYA1upOYKtcAlSg2o3M/0oQ+VzDvqtj0gQtukS2klhlADJ wcuE6igaJrKoesVCPrpimThZzoGoyhNWhz7nNgy38wq0t8ypvrtevF/Vfvv/8C2V2tnr LZYg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=vDOTn1DHFWC9cnru/L/wXqu3a7bO9S++Ez2vDwcQwsc=; b=q4VD++TyEaJqAtEFDBIZozO9fgWj4BIoZnfQKctKn+642nQlj/+TEHvHCdB9g2WsOi FaAuPHV9QXec4h98tA99AdcR+ydT/cik5uh89EBv1jHTMhEs+TCGJd8yaNDqAVNrACsQ c0X7rPQLNS6P2HJ5QnR/T2kx0JCWlSlFHTQdFETYWnSJofc4csuduIDNOH/vixwu9gSL 8i7V5ft6FOmVRPvU80SgF2qFQ+5Ig5Q8B4N7U49Fb/aCNVTRxGxaqGAAXqZtacdjoAhJ mz5dFBmweX/zCB8TZvtg7uviGT8sBseFOA6ufEA+jDFL6xNPguZmB933p9wSf613wXu9 0yfA== X-Gm-Message-State: APjAAAV7y1ionMgAYNdAWKSVlrdLTcTKQbp6VtrmYElGNcWJSz1XZVei ckNmKm42a2nr1sDtdCub5CXvqdYuL9665kQYuvv9vDBueBaYdw== X-Google-Smtp-Source: APXvYqy99sjs3IlDa+6wdiXl1Av5GjB+SRv0tZeeH6vcgof12/m4/CC7wsALXXJj1p8PSUlxbxnWUI6ZtQG/PRemVaw= X-Received: by 2002:a05:6512:48f:: with SMTP id v15mr23350086lfq.37.1565712884773; Tue, 13 Aug 2019 09:14:44 -0700 (PDT) MIME-Version: 1.0 References: <53b1d3a7753446099f24cafcd9de9d9f@metricly.com> In-Reply-To: From: Oleksandr Shulgin Date: Tue, 13 Aug 2019 18:14:18 +0200 Message-ID: Subject: Re: To Repair or Not to Repair To: User Content-Type: multipart/alternative; boundary="000000000000516cf9059001f070" --000000000000516cf9059001f070 Content-Type: text/plain; charset="UTF-8" On Thu, Mar 14, 2019 at 9:55 PM Jonathan Haddad wrote: > My coworker Alex (from The Last Pickle) wrote an in depth blog post on > TWCS. We recommend not running repair on tables that use TWCS. > > http://thelastpickle.com/blog/2016/12/08/TWCS-part1.html > Hi, I was wondering about this again, as I've noticed one of the nodes in our cluster accumulating ten times the number of files compared to the average across the rest of cluster. The files are all coming from a table with TWCS and repair (running with Reaper) is ongoing. The sudden growth started around 24 hours ago as the affected node was restarted due to failing AWS EC2 System check. Now I'm thinking again if we should be running those repairs at all. ;-) In the Summary of the blog post linked above, the following is written: It is advised to disable read repair on TWCS tables, and use an agressive tombstone purging strategy as digest mismatches during reads will still trigger read repairs. Was it meant to read "disable anti-entropy repair" instead? I find it confusing otherwise. Regards, -- Alex --000000000000516cf9059001f070 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Thu, Mar 14, 2019 at 9:55 PM Jonathan = Haddad <jon@jonhaddad.com> w= rote:
My coworker Alex (from The Last Pickle) w= rote an in depth blog post on TWCS.=C2=A0 We recommend not running repair o= n tables that use TWCS.


<= /div>
Hi,

I was wondering about this again, as= I've noticed one of the nodes in our cluster accumulating ten times th= e number of files compared to the average across the rest of cluster.=C2=A0= The files are all coming from a table with TWCS and repair (running with R= eaper) is ongoing.=C2=A0 The sudden growth started around 24 hours ago as t= he affected node was restarted due to failing AWS EC2 System check.=C2=A0 N= ow I'm thinking again if we should be running those repairs at all. ;-)=

In the Summary of the blog post linked above, the= following is written:

It is advised to disable read repair on TWCS tables, and use an agressiv= e tombstone purging strategy as digest mismatches during reads will still t= rigger read repairs.=C2=A0

Was it meant to read "disable anti-entro= py repair" instead?=C2=A0 I find it confusing otherwise.
Regards,
--
Alex

=
--000000000000516cf9059001f070--