Jeff Ferland created CASSANDRA-10862:
----------------------------------------
Summary: LCS repair: compact tables before making available in L0
Key: CASSANDRA-10862
URL: https://issues.apache.org/jira/browse/CASSANDRA-10862
Project: Cassandra
Issue Type: Improvement
Components: Compaction, Streaming and Messaging
Reporter: Jeff Ferland
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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)