You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Simon Zhou (JIRA)" <ji...@apache.org> on 2017/06/14 18:43:01 UTC
[jira] [Commented] (CASSANDRA-10862) LCS repair: compact tables
before making available in L0
[ https://issues.apache.org/jira/browse/CASSANDRA-10862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16049505#comment-16049505 ]
Simon Zhou commented on CASSANDRA-10862:
----------------------------------------
[~chenshen] Are you still working on this?
> 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
> Assignee: Chen Shen
> Labels: lcs
>
> 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.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org