"It is not possible to mix sequential repair and incremental repairs."
I guess that is a system limitation, even if I am not sure of it (I don't have used C*2.1 yet) I would focus on tuning your repair by : - Monitoring performance / logs (see why the cluster hangs) - Use range repairs (as a workaround to the Merkle tree 32K limit) or at list run it per table ( http://www.datastax.com/dev/blog/advanced-repair-techniques) Depending on what's the root issue that makes hang your cluster it is hard to help you. - If CPU is a limit, then some tuning around compactions or GC might be needed (or a few more things) - if you have Disk IO limitations, you might want to add machines or tune compaction throughput - If your network is the issue, there are commands to tune the bandwidth used by streams. You need to troubleshot this and give us more informations. I hope you have a monitoring tool up and running and an easy way to detect errors on your logs. C*heers, Alain 2015-06-26 16:26 GMT+02:00 Carl Hu <m...@carlhu.com>: > Dear colleagues, > > We are using incremental repair and have noticed that every few repairs, > the cluster experiences pauses. > > We run the repair with the following command: nodetool repair -par -inc > > I have tried to run it not in parallel, but get the following error: > "It is not possible to mix sequential repair and incremental repairs." > > Does anyone have any suggestions? > > Many thanks in advance, > Carl > >
