I recommend using cassandra-reaper Using crons without proper Monitoring will most likely not work as expected. There are some reaper forks on GitHub. You have to check which one works with your Cassandra version. The original one from Spotify only works on 2.x not on 3.x
Am 25.11.2016 07:31 schrieb "wxn...@zjqunshuo.com" <wxn...@zjqunshuo.com>: > Hi Artur, > When I asked similar questions, someone addressed me to the below links > and they are helpful. > > See http://www.datastax.com/dev/blog/repair-in-cassandra > https://lostechies.com/ryansvihla/2015/09/25/cassandras-repair-should-be- > called-required-maintenance/ > https://cassandra-zone.com/understanding-repairs/ > > Cheers, > -Simon > > *From:* Artur Siekielski <a...@vhex.net> > *Date:* 2016-11-10 04:22 > *To:* user <user@cassandra.apache.org> > *Subject:* repair -pr in crontab > Hi, > the docs give me an impression that repairing should be run manually, > and not put in crontab for default. Should each repair run be monitored > manually? > > If I would like to put "repair -pr" in crontab for each node, with a few > hour difference between the runs, are there any risks with such setup? > Specifically: > - if two or more "repair -pr" runs on different nodes are running at the > same time, can it cause any problems besides high load? > - can "repair -pr" be run simultaneously on all nodes at the same time? > - I'm using the default gc_grace_period of 10 days. Are there any > reasons to run repairing more often that once per 10 days, for a case > when previous repairing fails? > - how to monitor start and finish times of repairs, and if the runs were > successful? Does the "nodetool repair" command is guaranteed to exit > only after the repair is finished and does it return a status code to a > shell? > >
