In Cassandra 3.0 the default nodetool repair behaviour is incremental and
parallel.
Is there a downside to triggering repair from multiple nodes at the same
time?

Basically, instead of scheduling a cron job on one node to run repair, I
want to schedule the job on every node (this way, I don't have to worry
about repair if the one node goes down). Alternatively, I could build a
smarter solution for HA repair jobs, but that seems like an overkill.

Reply via email to