Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
Received-SPF: pass (nike.apache.org: domain of ailinykh@gmail.com designates
 209.85.217.181 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <707A7CFA945C43CDA59339E07765EF38@addthis.com>
References: <707A7CFA945C43CDA59339E07765EF38@addthis.com>
Date: Thu, 8 Aug 2013 17:56:55 -0700
Message-ID: 
 <CAK0tFt6TLV9ZRA+Mj+4y=95xMwgxPatWY2Vb8rKEQvS7cjH+iA@mail.gmail.com>
Subject: Re: Cassandra nodetool repair question
From: Andrey Ilinykh <ailinykh@gmail.com>
To: user@cassandra.apache.org
Content-Type: multipart/alternative; boundary=089e0158c5163c0f3d04e379408b

--089e0158c5163c0f3d04e379408b
Content-Type: text/plain; charset=ISO-8859-1

nodetool repair just triggers repair procedure. You can kill nodetool after
start, it doesn't change anything. To stop repair you have to use nodetool
stop VALIDATION|COMPACTION


Thank you,

  Andrey


On Thu, Aug 8, 2013 at 1:00 PM, Andy Losey <andrew@addthis.com> wrote:

>  Afternoon,
>
> We are noticing nodetool repair processes are not completing after a weeks
> worth of time, and have resulted in some Cassandra nodes having more than
> one process running do to cron scheduled. We are also chasing some
> performance degradation after upgrading all nodes to version 1.2.8 last
> Friday and would like to resolve this multiple repairs running at once
> issue in an effort to troubleshoot our performance issues.
>
> We'd like to know more about what is happening with the repair option. Is
> there a way to gracefully terminate them or any adverse affect to killing
> the processes we should look out for?
>
> Thanks,
> --
> Andy L
>
>

--089e0158c5163c0f3d04e379408b
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">nodetool repair just triggers repair procedure. You can ki=
ll nodetool after start, it doesn&#39;t change anything. To stop repair you=
 have to use nodetool stop VALIDATION|COMPACTION<div><br></div><div><br></d=
iv>
<div>Thank you,</div><div><br></div><div>=A0 Andrey</div><div><br></div></d=
iv><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Thu, Au=
g 8, 2013 at 1:00 PM, Andy Losey <span dir=3D"ltr">&lt;<a href=3D"mailto:an=
drew@addthis.com" target=3D"_blank">andrew@addthis.com</a>&gt;</span> wrote=
:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
                <div>
                    Afternoon,
                </div><div><br></div><div>We are noticing nodetool repair p=
rocesses are not completing after a weeks worth of time, and have resulted =
in some Cassandra nodes having more than one process running do to cron sch=
eduled. We are also chasing some performance degradation after upgrading al=
l nodes to version 1.2.8 last Friday and would like to resolve this multipl=
e repairs running at once issue in an effort to troubleshoot our performanc=
e issues.</div>
<div><br></div><div>We&#39;d like to know more about what is happening with=
 the repair option. Is there a way to gracefully terminate them or any adve=
rse affect to killing the processes we should look out for?</div><div><br>
</div><div>Thanks,</div><span class=3D"HOEnZb"><font color=3D"#888888"><div=
><div>--=A0</div><div>Andy L</div><div><br></div></div>
            </font></span></blockquote></div><br></div>

--089e0158c5163c0f3d04e379408b--