> If you do not feel ready for incremental repairs, just adding the '-full'
option to your 'nodetool repair' command should be enough to continue
repairing as you currently are once using 3.0.7.
This is not entirely true on 2.2+ after CASSANDRA-7586, since
anti-compaction is always executed after
Hi Jean,
Our concern is the repair, in 3.0.7 repairs inc are by default. Then it
> means that once we do the upgrade to 3.0.7 we must follow the migration
> process of repairs inc for all our data in order to mark the sstables as
> repaired ?
If you do not feel ready for incremental repairs, jus
Migration procedure is no longer required for incremental repair as of
2.1.4 since CASSANDRA-8004, which was the reason why the migration
procedure was required for LCS before. The migration procedure is only
useful now to skip validation on already repaired sstables in the first
incremental repair
Hello guys
We are planing to upgrade cassandra soon to the version 3.0.7 from 2.1.14.
Our concern is the repair, in 3.0.7 repairs inc are by default. Then it
means that once we do the upgrade to 3.0.7 we must follow the migration
process of repairs inc for all our data in order to mark the sstable
