!
From: Paulo Motta [mailto:pauloricard...@gmail.com]
Sent: Wednesday, September 28, 2016 5:16 AM
To: user@cassandra.apache.org
Subject: Re: Repairs at scale in Cassandra 2.1.13
There were a few streaming bugs fixed between 2.1.13 and 2.1.15 (see
CHANGES.txt for more details), so I'd recommen
There were a few streaming bugs fixed between 2.1.13 and 2.1.15 (see
CHANGES.txt for more details), so I'd recommend you to upgrade to 2.1.15 in
order to avoid having those.
2016-09-28 9:08 GMT-03:00 Alain RODRIGUEZ :
> Hi Anubhav,
>
>
>> I’m considering doing subrange repairs (https://github.com
Hi Anubhav,
> I’m considering doing subrange repairs (https://github.com/
> BrianGallew/cassandra_range_repair/blob/master/src/range_repair.py)
>
I used this script a lot, and quite successfully.
An other working option that people are using is:
https://github.com/spotify/cassandra-reaper
Ale
Hello,
We run Cassandra 2.1.13 (don't have plans to upgrade yet). What is the best way
to run repairs at scale (400 nodes, each holding ~600GB) that actually works ?
I'm considering doing subrange repairs
(https://github.com/BrianGallew/cassandra_range_repair/blob/master/src/range_repair.py)
a
