[CASSANDRA-8858] Avoid not doing anticompaction on compacted away sstables

• Type: Improvement
• Status: Resolved
• Priority: Normal
• Resolution: Duplicate
• Assignee: Unassigned
• Reporter: Marcus Eriksson
• Created: 24/Feb/15 12:33
• Updated: 16/Apr/19 09:31
• Resolved: 29/Aug/16 07:11

Description

Currently, if an sstable is compacted away during repair, we will not anticompact it, meaning we will do too much work when we run the next repair.

There are a few ways to solve this:
1. track where the compacted sstables end up (ie, we compact and sstable 1,2 that are being repaired into sstable 3, we can anticompact sstable 3 once repair is done). Note that this would force us to not compact newly flushed sstables with the ones that existed when we started repair.
2. don't do compactions at all among the sstables we repair (essentially just mark the as compacting when we start validating and keep them that way throughout the repair)

Issue Links

• duplicates: CASSANDRA-9143 Fix consistency of incrementally repaired data across replicas