[CASSANDRA-5351] Avoid repairing already-repaired data by default

• Type: Task
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 2.1 beta1
• Labels: qa-resolved repair
• Assignee: Lyuben Todorov
• Reporter: Jonathan Ellis

Authors

Lyuben Todorov

Reviewers

Marcus Eriksson

• Tester: Shawn Kumar
• Created: 14/Mar/13 22:04
• Updated: 16/Apr/19 09:32
• Resolved: 08/Feb/14 07:50

Description

Repair has always built its merkle tree from all the data in a columnfamily, which is guaranteed to work but is inefficient.

We can improve this by remembering which sstables have already been successfully repaired, and only repairing sstables new since the last repair. (This automatically makes CASSANDRA-3362 much less of a problem too.)

The tricky part is, compaction will (if not taught otherwise) mix repaired data together with non-repaired. So we should segregate unrepaired sstables from the repaired ones.

Issue Links

• is related to: CASSANDRA-7250 Make incremental repair default in 3.0
• relates to: CASSANDRA-7892 Hashmap IllegalStateException in anticompaction
• supercedes: CASSANDRA-7887 Skip completing a streamed file if it is identical to one of local files