Complete repair after switching to incremental repair of Cassandra nodes

Question

We are currently running Cassandra v 3.0.5 on all our nodes. We recently relocated our units to perform incremental repairs. However, the documentation says that incremental repairs should be performed daily and complete repairs weekly or monthly. We perform parallel incremental repairs on each node by running

nodetool repair

And we will form a consistent full repair on each node by running

nodetool repair -full -seq

I take care to complete the repair from the moment of transfer. Can I just use the above command on each of the nodes or any other steps that I should perform first? I just want to make sure that we do not need to perform such steps as those that we used in the migration process:

• Disable auto-resistance on node.
• Run a complete, consistent repair.
• Stop node.
• Set the repairedAt metadata value for each SSTable that existed before you turned off compression.
• Restart Cassandra on node.
• Enable auto-resistance on node.

Any advice would be appreciated. Thanks.

Answer 1

This answer may come much later than you wanted, but no, you do not need to do these steps. If you are having trouble repairing large partitions, I recommend that you use Reaper . In fact, this tool is so useful that I suggest you use it anyway.