Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
Received-SPF: pass (athena.apache.org: domain of edlinuxguru@gmail.com
 designates 209.85.214.44 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :cc:content-type:content-transfer-encoding;
        b=amNg+zvCHSZ7Dop8u8Zyo50IEd8iNHju8qsPtzJoOnBNevEOvSTTvUldUqrosNTzVj
         hZriyYYvgVaQlTYZCfgH42N9EOsouOOH1qFxKIx7s55QbErotVAkyKBb2XEPirWUayCy
         WKhKPw0/eyk8y1/AsfPT+zZ91UCxzcaXEBTco=
MIME-Version: 1.0
In-Reply-To: <AANLkTineS0ps8q58MrEAj7EzsaL+MAtOkSNxAMoK9YH3@mail.gmail.com>
References: <1301420212192-6220171.post@n2.nabble.com>
	<AANLkTik0R1tNiFT0MZb=4_hZwZGYc2nvFU4KGAGFJuAC@mail.gmail.com>
	<1301421070734-6220228.post@n2.nabble.com>
	<AANLkTik+Fam7y48NXkN68pnQUMjOQckKJAiyv2yuOO2W@mail.gmail.com>
	<1301424132945-6220423.post@n2.nabble.com>
	<AANLkTimiroMp2Pg2138YiiEbyXJU8oDPx7xgHc+wmo8O@mail.gmail.com>
	<1301428784487-6220683.post@n2.nabble.com>
	<AANLkTin-WG_cHvdKAJ3VtS9OCyLxZopfpmps2QRdex1m@mail.gmail.com>
	<1301434571427-6221041.post@n2.nabble.com>
	<AANLkTi=d5baZ6RDXFKD+4ocgrCqvHHRF8Ui-8Sqo2HVt@mail.gmail.com>
	<1301436482271-6221157.post@n2.nabble.com>
	<AANLkTinz7x6=oAmEUWhvwvwi0bJCFHHPTAqVNTPX5bcW@mail.gmail.com>
	<4D92DBEF.2050105@hiramoto.org>
	<AANLkTineS0ps8q58MrEAj7EzsaL+MAtOkSNxAMoK9YH3@mail.gmail.com>
Date: Wed, 30 Mar 2011 13:25:35 -0400
Message-ID: <AANLkTinCXP25K9TNd4Vc3jCyMrqncYWUgJxjDdMq=v_u@mail.gmail.com>
Subject: Re: How to determine if repair need to be run
From: Edward Capriolo <edlinuxguru@gmail.com>
To: user@cassandra.apache.org
Cc: Peter Schuller <peter.schuller@infidyne.com>,
 Karl Hiramoto <karl@hiramoto.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Wed, Mar 30, 2011 at 12:54 PM, Peter Schuller
<peter.schuller@infidyne.com> wrote:
>> Note this script doesn't work if your repair takes hours, and in the
>> middle of the repair cassandra was restarted, nodetool will exit and the
>> flagfile will be updated. =A0 Another case, if repair hangs, and day lat=
er
>> cassandra is restarted.
>
> This is why "set -e" is at the to and commented as "important" :) But
> it relies on 'nodetool repair' reliably exiting with non-zero exit
> status on failures.
>
>> if nodetool returns an error this might work:
>>
>> =A0nodetool -h localhost repair && touch /path/to/flagfile.tmp
>
> That's the equivalent, due to 'set -e'.
>
>
> --
> / Peter Schuller
>

I just wanted to chime in here and say some people NEVER run repair.
In our particular case we remove inactive data older then a specific
date. If we lost a tombstone and that data were to re-appear that
would really not be the end of the world for us. Repair is really
intensive since it involves a compaction and in 0.6.X was not optimal
as it really increased on disk data. I have followed some threads and
there are some conditions that I read repair can't handle. The
question you have to ask yourself is how likely are they to occur and
what they might mean in your use-case. These are not easy questions to
answer.