From user-return-61157-archive-asf-public=cust-asf.ponee.io@cassandra.apache.org Thu May 24 11:17:19 2018 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 [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id 01AEC18077D for ; Thu, 24 May 2018 11:12:56 +0200 (CEST) Received: (qmail 28209 invoked by uid 500); 24 May 2018 09:12: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 28198 invoked by uid 99); 24 May 2018 09:12:55 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 24 May 2018 09:12:55 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id D95CFC0157 for ; Thu, 24 May 2018 09:12:54 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.879 X-Spam-Level: * X-Spam-Status: No, score=1.879 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_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd4-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id iFFfqH06252R for ; Thu, 24 May 2018 09:12:49 +0000 (UTC) Received: from mail-vk0-f42.google.com (mail-vk0-f42.google.com [209.85.213.42]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id 8DC9D5F485 for ; Thu, 24 May 2018 09:12:48 +0000 (UTC) Received: by mail-vk0-f42.google.com with SMTP id x191-v6so539426vke.10 for ; Thu, 24 May 2018 02:12:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=Feh8v8GgFuB2XBUdj9t9mVcxQkYOjG4JB2WIaPe7oAY=; b=WfWMcbZEDxADlySSqq2B6fccpnFW19j8g2lhO6UJsvp7qQ3I9PziirzbpiyP/jMbXn esjNVLhWeuB2RI7DLpg5UMXHmtAXzFujY17EnrX681T/aJMtLR30+1NNGgIxSTrfyXWk lGX1y05P0jl0azG5xPUK3PMgPJaf7m2jRSxi6ioQ82gkedvM++1Jq4PapOmWnIHqY/ZK 71juzk2ehtOLbeYrIfVHE1WY1S+Et7jLVGYiDUDOkCAdl6OssNpE1sykQjDDG7Kk7++l FLJaKoael2lIQJiXKJi9zGBt/Eph5h60bA99cenRBd4Wj8dIVvx2DZluXmeR/PUbpj5j iYFQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=Feh8v8GgFuB2XBUdj9t9mVcxQkYOjG4JB2WIaPe7oAY=; b=jWDB9Vy6iQx5bHq/ePK3cObTYMxlW7hfShd9mY5tW10FNWNm2jqHWKO5xmzu/zoOZB OdvO5eMMuW/vku4d3NAiO28ASzirimx9OXjDx0T1AxspbyEYR9K5Npgl8ouQhXyCcUGC 7G1Z9i+bGBHWNjxzpNZZyv6dEoDqi7tcMq0FVbXyTlxf9oU6mKek0S3kVNo8P2Rd4gzl d4SYuJipo9CX2/+8wIegHnBAx8uKBf2jrYqLdiYE3K+O6PkLc3gmnNxBZaTDARYr5E/T Yhxrountpx346OWVp0R1OQk2do2kxcfDSVs8XhxYPbsl1a9lJEOtw14Qq46SBVZ9bgDw /dtQ== X-Gm-Message-State: ALKqPwfe3MCEfnFQqN2P0O7cPN97+kVmA2p3MUyowM7Wn7VDBA5mKAvV RVkRWwrboAfpwhVGZU0UGqYBStZ5B6AtOtQhF/s2sHmo X-Google-Smtp-Source: AB8JxZofFbtorL1m9eZZni8AvObW/wxb6imyGTyveqse0Ufer+gTvb5IzTTcQSImszC45ZgUMH+dvz1gD5+ynjRw5Kk= X-Received: by 2002:a1f:7c83:: with SMTP id x125-v6mr4114775vkc.28.1527153166981; Thu, 24 May 2018 02:12:46 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a67:360c:0:0:0:0:0 with HTTP; Thu, 24 May 2018 02:12:26 -0700 (PDT) In-Reply-To: References: From: Alain RODRIGUEZ Date: Thu, 24 May 2018 10:12:26 +0100 Message-ID: Subject: Re: repair in C* 3.11.2 and anticompactions To: "user cassandra.apache.org" Content-Type: multipart/alternative; boundary="000000000000092096056cf00e75" --000000000000092096056cf00e75 Content-Type: text/plain; charset="UTF-8" Hi Jean, Here is what Alexander wrote about it, a few months ago, in the comments of the article mentioned above: "A full repair is an incremental one that doesn't skip repaired data. > Performing anticompaction in that case too (regardless it is a valid > approach or not) allows to mark as repaired SSTables that weren't before > the full repair was started. > > It was clearly added with the intent of making full repair part of a > routine where incremental repairs are also executed, leaving only subrange > for people who do not want to use incremental. > > One major drawback is that by doing so, the project increased the > operational complexity of running full repairs as it does not allow > repairing the same keyspace from 2 nodes concurrently without risking some > failures during validation compaction (when an SSTable is being > anticompacted, it cannot go through validation compaction)." > > I hope this helps, C*heers, ----------------------- Alain Rodriguez - @arodream - alain@thelastpickle.com France / Spain The Last Pickle - Apache Cassandra Consulting http://www.thelastpickle.com 2018-05-23 21:48 GMT+01:00 Lerh Chuan Low : > Hey Jean, > > I think it still does anticompaction by default regardless, it will not do > so only if you do subrange repair. TLP wrote a pretty good article on that: > http://thelastpickle.com/blog/2017/12/14/should- > you-use-incremental-repair.html > > On 24 May 2018 at 00:42, Jean Carlo wrote: > >> Hello >> >> I just want to understand why, if I run a repair non incremental like this >> >> nodetool -h 127.0.0.1 -p 7100 repair -full -pr keyspace1 standard1 >> >> Cassandra does anticompaction as the logs show >> >> INFO [CompactionExecutor:20] 2018-05-23 16:36:27,598 >> CompactionManager.java:1545 - Anticompacting [BigTableReader(path='/home/jr >> iveraura/.ccm/test/node1/data0/keyspace1/standard1-36a6ec405 >> e9411e8b1d1b38a73559799/mc-2-big-Data.db')] >> >> As far as I understood the anticompactions are used to make the repair >> incremantals possible, so I was expecting no having anticompactions making >> repairs with the options -pr -full >> >> Anyone knows why does cassandra make those anticompactions ? >> >> Thanks >> >> Jean Carlo >> >> "The best way to predict the future is to invent it" Alan Kay >> > > --000000000000092096056cf00e75 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi Jean,

Here is what Alexander wrote a= bout it, a few months ago, in the comments of the article mentioned above:<= br>

"A full repair is = an incremental one that doesn't skip repaired data. Performing anticomp= action in that case too (regardless it is a valid approach or not) allows t= o mark as repaired SSTables that weren't before the full repair was sta= rted.

It was clearly added with the intent of making full repair part of a ro= utine where incremental repairs are also executed, leaving only subrange fo= r people who do not want to use incremental.

One major drawback is that by doing so, t= he project increased the operational complexity of running full repairs as = it does not allow repairing the same keyspace from 2 nodes concurrently wit= hout risking some failures during validation compaction (when an SSTable is= being anticompacted, it cannot go through validation compaction)."


=C2=A0I hope this helps,
<= div>
C*heers,
-----------------------
Alain Rodriguez - @arodream - = alain@thelastpickle.com
France / Spain

The Last Pickle - Apache Cassandra Consulting=

2018-05-23 21:48 = GMT+01:00 Lerh Chuan Low <lerh@instaclustr.com>:
Hey Jean,=C2=A0

I think i= t still does anticompaction by default regardless, it will not do so only i= f you do subrange repair. TLP wrote a pretty good article on that:=C2=A0http://thelastpickle.com/blog/2017/12/= 14/should-you-use-incremental-repair.html

On 24 May 2018 at 00:42, Jean Carlo <jean.jeancarl48@gma= il.com> wrote:
Hello

I just want to understand why, if I run = a repair non incremental like this

nodetool -h 127.0.0.1 -p 7100 repair -full -pr keyspace1 sta= ndard1

Cassandra does anticompaction as the logs show
INFO=C2=A0 [Compactio= nExecutor:20] 2018-05-23 16:36:27,598 CompactionManager.java:1545 - Anticom= pacting [BigTableReader(path=3D'/home/jriveraura/.ccm/test/node1/d= ata0/keyspace1/standard1-36a6ec405e9411e8b1d1b38a73559799/mc-2-big-Data.db')]

=
<= div dir=3D"ltr">
As far as I und= erstood the anticompactions are used to make the repair incremantals possib= le, so I was expecting no having anticompactions making repairs with the op= tions=C2=A0 -pr -full

Anyone knows why does cassandra make those anticompactions ? <= br>

=
Thanks

Jean Ca= rlo

"The best way to predict the future is to invent it"= ; Alan Kay


--000000000000092096056cf00e75--