Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
MIME-Version: 1.0
In-Reply-To: 
 <CAJ=3xgRKt8kYHMZwihQpdH25O_6mT2xaR3QK2vgeX4Rm2qT7Mw@mail.gmail.com>
References: 
 <CAJ=3xgSfcZbs4=BwKveZhF5wh+gSJumghqYLU0uAHZPd9+QDzA@mail.gmail.com>
	<CAEDUwd20V3SbyP_3T69HC1eqLpKqg=T-pnb+F-H3ZrvoxAD3-Q@mail.gmail.com>
	<CAJ=3xgRKt8kYHMZwihQpdH25O_6mT2xaR3QK2vgeX4Rm2qT7Mw@mail.gmail.com>
Date: Mon, 17 Aug 2015 11:31:06 -0700
Message-ID: 
 <CAEDUwd1KvfnO151hJ-qW3sNs0oQ10_Ypzu2K=z3acxsghkHFwQ@mail.gmail.com>
Subject: Re: Parallel repairs
From: Robert Coli <rcoli@eventbrite.com>
To: "user@cassandra.apache.org" <user@cassandra.apache.org>
Content-Type: multipart/alternative; boundary=001a11c3cb62363047051d8601eb

--001a11c3cb62363047051d8601eb
Content-Type: text/plain; charset=UTF-8

On Mon, Aug 17, 2015 at 8:50 AM, Stan Lemon <slemon@salesforce.com> wrote:,
>
> Thanks for the reply.  I do have vnodes.  I was not aware of the -par flag
> on the repair command, I was actually referring to have repair run on both
> nodes A & B at the same time.  It sounds like though, that I should
> probably be using this -par flag but to do it per node sequentially one
> after the other?
>

That's what I was suggesting, yes.


> Right now just running 'nodetool repair' on one node is taking ~3.5 days,
> with 24 nodes I am now starting to question whether or not I should be
> increasing gc_grace_second to be much longer than the default 10 days since
> it's going to take longer than 10 days to repair the whole cluster.
>

Yep, I personally recommend setting it to 34 days and then kicking off
repair on the first of the month. That way you have been 3 and 7 days for
it to complete, which should in most cases be enough time.

Have you unthrottled compaction and etc.? 10 days is a long time...

=Rob

--001a11c3cb62363047051d8601eb
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On M=
on, Aug 17, 2015 at 8:50 AM, Stan Lemon <span dir=3D"ltr">&lt;<a href=3D"ma=
ilto:slemon@salesforce.com" target=3D"_blank">slemon@salesforce.com</a>&gt;=
</span> wrote:,<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex=
;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div>Thanks =
for the reply.=C2=A0 I do have vnodes.=C2=A0 I was not aware of the -par fl=
ag on the repair command, I was actually referring to have repair run on bo=
th nodes A &amp; B at the same time.=C2=A0 It sounds like though, that I sh=
ould probably be using this -par flag but to do it per node sequentially on=
e after the other?</div></div></blockquote><div><br></div><div>That&#39;s w=
hat I was suggesting, yes.</div><div>=C2=A0</div><blockquote class=3D"gmail=
_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:=
1ex"><div dir=3D"ltr"><div>Right now just running &#39;nodetool repair&#39;=
 on one node is taking ~3.5 days, with 24 nodes I am now starting to questi=
on whether or not I should be increasing gc_grace_second to be much longer =
than the default 10 days since it&#39;s going to take longer than 10 days t=
o repair the whole cluster.</div></div></blockquote><div><br></div><div>Yep=
, I personally recommend setting it to 34 days and then kicking off repair =
on the first of the month. That way you have been 3 and 7 days for it to co=
mplete, which should in most cases be enough time.</div><div><br></div><div=
>Have you unthrottled compaction and etc.? 10 days is a long time...<br></d=
iv><div><br></div><div>=3DRob</div><div><br></div></div></div></div>

--001a11c3cb62363047051d8601eb--