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 C18E1200BA5 for ; Wed, 19 Oct 2016 19:09:14 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id C020D160AEA; Wed, 19 Oct 2016 17:09:14 +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 B761F160ADC for ; Wed, 19 Oct 2016 19:09:13 +0200 (CEST) Received: (qmail 89683 invoked by uid 500); 19 Oct 2016 17:09:12 -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 89673 invoked by uid 99); 19 Oct 2016 17:09:12 -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; Wed, 19 Oct 2016 17:09:12 +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 B48AEC0595 for ; Wed, 19 Oct 2016 17:09:11 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.78 X-Spam-Level: * X-Spam-Status: No, score=1.78 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=2, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RCVD_IN_SORBS_SPAM=0.5] autolearn=disabled Authentication-Results: spamd4-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=thelastpickle-com.20150623.gappssmtp.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 CofVAKxhtvmA for ; Wed, 19 Oct 2016 17:09:07 +0000 (UTC) Received: from mail-qt0-f174.google.com (mail-qt0-f174.google.com [209.85.216.174]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id 078A95F1D5 for ; Wed, 19 Oct 2016 17:09:01 +0000 (UTC) Received: by mail-qt0-f174.google.com with SMTP id q7so28836948qtq.1 for ; Wed, 19 Oct 2016 10:09:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=thelastpickle-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=Otj/mpSM1EFKEPJLi5D/St8J5mH59WMEtKJLjUvN/KM=; b=DWiuAPQIK/0RacWmEprv4Hg2kIwZz/1mQtxrf79wU9s+pMH5HJcU+BChAQAt06/8dl CAC4vo1hlGRZMcS5sUiMKTjm7Z35doHT2HHEb4uhNBGk5noAOiuW8O6ftGfM4XOfVyoT 99OH4CPTkdpbJZiReusKnNwsoOAJ80iiDskM5Jkl7KPHZLWQ/JWP9N310nFwuLv2KuEy VIoUW1MWYprXjEClJL45hRZQJf+aehut3j1oqMGWGQWbU/rUN509MyJQmOv4y0HK3hj4 3KCJD+K9rfERnS7uejk4FPw4eT+hTIbToAupcnDMqTQ07WdxjoQGYH8Yr1SrsN/flNbR CK1w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=Otj/mpSM1EFKEPJLi5D/St8J5mH59WMEtKJLjUvN/KM=; b=jEmlJnw+M3Dryto79TCXxj1GpMeKaD4hU5Imy3SiEugJvlA658kfRZvBe0ehli4kQh eR3IA1AlVzr1GkSXGCGGD0Cyefh1M1FtuWg/kl61LTKtjBSJAfFs8fZIlelDgDWNvOVx n8/XeGrDHCXI0oYBb4kRU8Ao9Z1QUpJ/zaw0JifWiAUsRI4wp7UdwpNRHBP53b0SLY8Q 0pOXGVt4lUHMBrSxVSk9ESgK0LBfU+lp5YV63Et1DeeQM+5WI4D7KLodU87wIzl2O9PC uBYRINjRYg2a02y4C8IelnMB/CCMcZLhCINEHdas1QRxb5lZQGFKpElGAEdomwwVbOGI 4i3A== X-Gm-Message-State: AA6/9Rmc3iVQkm1X3PPSMpImUnLdPCWMi13Cq9Mjm1RENpp/45LijdOG98mL13ojeQ5ICPoCdfD5yb3pW26zrg== X-Received: by 10.194.177.230 with SMTP id ct6mr5058120wjc.145.1476896938722; Wed, 19 Oct 2016 10:08:58 -0700 (PDT) MIME-Version: 1.0 References: <70E49EAD-F578-4685-AF2D-19CCB63310F5@peernova.com> In-Reply-To: <70E49EAD-F578-4685-AF2D-19CCB63310F5@peernova.com> From: Alexander Dejanovski Date: Wed, 19 Oct 2016 17:08:47 +0000 Message-ID: Subject: Re: non incremental repairs with cassandra 2.2+ To: user@cassandra.apache.org Content-Type: multipart/alternative; boundary=089e013d1d9c67205e053f3addda archived-at: Wed, 19 Oct 2016 17:09:14 -0000 --089e013d1d9c67205e053f3addda Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Can you explain why you would want to run repair for new nodes? Aren't you talking about bootstrap, which is not related to repair actually= ? Le mer. 19 oct. 2016 18:57, Kant Kodali a =C3=A9crit : > Thanks! How do I do an incremental repair when I add a new node? > > Sent from my iPhone > > On Oct 19, 2016, at 9:54 AM, Alexander Dejanovski > wrote: > > Hi Kant, > > subrange is a form of full repair, so it will just split the repair > process in smaller yet sequential pieces of work (repair is started givin= g > a start and end token). Overall, you should not expect improvements other > than having less overstreaming and better chances of success if your > cluster is dense. > > You can try to use incremental repair if you know what the caveats are an= d > use a proper tool to orchestrate it, that would save you from repairing a= ll > 10TB each time. > CASSANDRA-12580 might help too as Romain showed us : > https://www.mail-archive.com/user@cassandra.apache.org/msg49344.html > > Cheers, > > > > On Wed, Oct 19, 2016 at 6:42 PM Kant Kodali wrote: > > Another question on a same note would be what would be the fastest way to > do repairs of size 10TB cluster ? Full repairs are taking days. So among > repair parallel or repair sub range which is faster in the case of say > adding a new node to the cluster? > > Sent from my iPhone > > On Oct 19, 2016, at 9:30 AM, Sean Bridges > wrote: > > Hey, > > We are upgrading from cassandra 2.1 to cassandra 2.2. > > With cassandra 2.1 we would periodically repair all nodes, using the -pr > flag. > > With cassandra 2.2, the same repair takes a very long time, as cassandra > does an anti compaction after the repair. This anti compaction causes mo= st > (all?) the sstables to be rewritten. Is there a way to do full repairs > without continually anti compacting? If we do a full repair on each node > with the -pr flag, will subsequent full repairs also force anti compactin= g > most (all?) sstables? > > Thanks, > > Sean > > -- > ----------------- > Alexander Dejanovski > France > @alexanderdeja > > Consultant > Apache Cassandra Consulting > http://www.thelastpickle.com > > -- ----------------- Alexander Dejanovski France @alexanderdeja Consultant Apache Cassandra Consulting http://www.thelastpickle.com --089e013d1d9c67205e053f3addda Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Can you explain why you would want to run repair for new nodes?

Aren't you talking about bootstrap, which is not related to rep= air actually?

Le mer. 19= oct. 2016 18:57, Kant Kodali <kant= @peernova.com> a =C3=A9crit=C2=A0:
Thank= s! How do I do an incremental repair when I add a new node?

Sent from my iPhone

= On Oct 19, 2016, at 9:54 AM, Alexander Dejanovski <alex@thelastpick= le.com> wrote:

=
Hi Ka= nt,

subrange is a form of full repair, so it will just split the repair= process in smaller yet sequential pieces of work (repair is started giving= a start and end token). Overall, you should not expect improvements other = than having less overstreaming and better chances of success if your cluste= r is dense.

You can try to use incremental repair if you know wha= t the caveats are and use a proper tool to orchestrate it, that would save = you from repairing all 10TB each time.
CASSAN= DRA-12580 might help too as Romain showed us :=C2=A0https://www.mail-archive.com/user@cassandra.apache.org= /msg49344.html

Cheers,



On Wed, Oct 19, 2016 at 6:42 PM Kant Kodali = <kant@peernova.com> wrote:
Another question on a same note would be what would be = the fastest way to do repairs of size 10TB cluster ? Full repairs are takin= g days. So among repair parallel or repair sub range which is faster in the= case of say adding a new node to the cluster?

Sent from my iPhone

On Oct 19, = 2016, at 9:30 AM, Sean Bridges <sean.bridges@globalrelay.net<= /a>> wrote:

=20 =20 =20 =20

Hey,<= /font>

We ar= e upgrading from cassandra 2.1 to cassandra 2.2.=C2=A0

With = cassandra 2.1 we would periodically repair all nodes, using the -pr flag.=C2=A0

With = cassandra 2.2, the same repair takes a very long time, as cassandra does an anti compaction after the repair.=C2=A0 This anti compaction causes most (all?) the sstables = to be rewritten.=C2=A0 Is there a way to do full repairs without conti= nually anti compacting?=C2=A0 If we do a full repair on each node with the -pr flag, will subsequent full repairs also force anti compacting most (all?) sstables?=C2=A0

Thank= s,

Sean<= /font>

=20
--
-----------------
Alexander Dejanovski
France
@alexanderdeja
Co= nsultant
Apache Cassandra= Consulting
http://w= ww.thelastpickle.com
--
<= /div>
-----------------
Alexander Dejan= ovski
France
@a= lexanderdeja

Consultant
Apache Cassandra Consulting
--089e013d1d9c67205e053f3addda--