If you're using DSE, you can schedule it automatically using the repair service. If you're open source, check out Spotify cassandra reaper, it'll manage it for you.
https://github.com/spotify/cassandra-reaper On Thu, Jun 18, 2015 at 12:36 PM Jean Tremblay < jean.tremb...@zen-innovations.com> wrote: > Hi, > > I want to make on a regular base repairs on my cluster as suggested by the > documentation. > I want to do this in a way that the cluster is still responding to read > requests. > So I understand that I should not use the -par switch for that as it will > do the repair in parallel and consume all available resources. > > If you issue a “nodetool repair” on one node will it repair all the nodes > in the cluster or only the one on which we issue the command? > > If it repairs only one node, do I have to wait that the nodetool repair > ends, and only then issue another “nodetool repair” on the next node? > > If we had down time periods I would issue a nodetool -par, but we don’t > have down time periods. > > Sorry for the stupid questions. > Thanks for your help.
