I would recommend adding something to C* to be able to flip the repaired
state on all sstables quickly (with default OSS can turn nodes off one at a
time and use sstablerepairedset). It's a life saver to be able to revert
back to non-IR if migration going south. Same can be used to quickly switch
i
The gc_grace_seconds, which default to 10 days, is the maximal safe
interval between repairs. How much data gets written during that period
of time? Will your nodes run out of disk space because of the new data
written during that time? If so, it sounds like your nodes are
dangerously close to
Hi folks,
One last question regarding incremental repair.
What would be a safe approach to temporarily stop running incremental
repair on a cluster (e.g.: during a Cassandra major version upgrade)? My
understanding is that if we simply stop running incremental repair, the
cluster's nodes can, in
