: user@cassandra.apache.org
Subject: RE: Periodic Anti-Entropy repair
We have encountered issues of very long running nodetool repair when we ran it
node by node on really large dataset. It even kept on running for a week in
some cases.
IMO the strategy you are choosing of repairing nodes by –st and
value. Better not use i+=2 because token values are not
necessarily even numbers.
Regards,
Tarun
From: Anuj Wadehra [mailto:anujw_2...@yahoo.co.in]
Sent: Sunday, May 24, 2015 6:31 AM
To: user@cassandra.apache.org
Subject: Re: Periodic Anti-Entropy repair
You should use nodetool repair -pr on
You should use nodetool repair -pr on every node to make sure that each range
is repaired only once.
Thanks
Anuj Wadehra
Sent from Yahoo Mail on Android
From:"Brice Argenson"
Date:Sat, 23 May, 2015 at 12:31 am
Subject:Periodic Anti-Entropy repair
Hi everyone,
We are currently migrating f
Did you have a look at Reaper? https://github.com/spotify/cassandra-reaper
it's a project created by Spotify to address this issue, I did not evaluate
it yet but it looks promising.
On May 22, 2015 9:01 PM, "Brice Argenson" wrote:
> Hi everyone,
>
> We are currently migrating from DSE to Apache
Hi everyone,
We are currently migrating from DSE to Apache Cassandra and we would like
to put in place an automatic and periodic *nodetool repair* execution to
replace the one executed by OpsCenter.
I wanted to create a script / service that would run something like that:
*token_rings = `node
