It is absolutely ok to run parallel repair -pr, if
1. the ranges do not overlap
2. if your cluster can handle the pressure - do not underestimate that.
In reaper you can tweak some settings like repair intensity to give your
cluster some time to breath between repair slices.
2016-11-25 11:34 GMT+
Hi,
yes, I read about how the repairing works, but the docs/blog posts lack
practical recommendations and "best practices". For example, I found
people having issues with running "repair -pr" simultaneously on all
nodes, but it isn't clear it shouldn't be allowed.
In the end I implemented rol
hla/2015/09/25/cassandras-repair-should-be-called-required-maintenance/
> https://cassandra-zone.com/understanding-repairs/
>
> Cheers,
> -Simon
>
> *From:* Artur Siekielski
> *Date:* 2016-11-10 04:22
> *To:* user
> *Subject:* repair -pr in crontab
> Hi,
> the docs give m
should-be-
> called-required-maintenance/
> https://cassandra-zone.com/understanding-repairs/
>
> Cheers,
> -Simon
>
> *From:* Artur Siekielski
> *Date:* 2016-11-10 04:22
> *To:* user
> *Subject:* repair -pr in crontab
> Hi,
> the docs give me an impression tha
/understanding-repairs/
Cheers,
-Simon
From: Artur Siekielski
Date: 2016-11-10 04:22
To: user
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
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
