[CASSANDRA-10862] LCS repair: compact tables before making available in L0

• Type: Improvement
• Status: Open
• Priority: Normal
• Resolution: Unresolved
• Component/s: Legacy/Streaming and Messaging, Local/Compaction
• Labels: lcs
• Assignee: Chen Shen
• Reporter: Jeff Ferland

Authors

Chen Shen

• Created: 14/Dec/15 21:18
• Updated: 16/Apr/19 09:30

Description

When doing repair on a system with lots of mismatched ranges, the number of tables in L0 goes up dramatically, as correspondingly goes the number of tables referenced for a query. Latency increases dramatically in tandem.

Eventually all the copied tables are compacted down in L0, then copied into L1 (which may be a very large copy), finally reducing the number of SSTables per query into the manageable range.

It seems to me that the cleanest answer is to compact after streaming, then mark tables available rather than marking available when the file itself is complete.

Issue Links

• is duplicated by: CASSANDRA-12940 Large compaction backlogs should slow down repairs
• relates to: CASSANDRA-11432 Counter values become under-counted when running repair.