You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "T Jake Luciani (JIRA)" <ji...@apache.org> on 2014/05/20 15:34:38 UTC
[jira] [Comment Edited] (CASSANDRA-7272) Add "Major" Compaction to
LCS
[ https://issues.apache.org/jira/browse/CASSANDRA-7272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14003225#comment-14003225 ]
T Jake Luciani edited comment on CASSANDRA-7272 at 5/20/14 1:32 PM:
--------------------------------------------------------------------
This may be accomplished also with CASSANDRA-6851 and CASSANDRA-7019
was (Author: tjake):
This may be accomplished also with CASSANDRA-6851 and CASSANDRA-7109
> Add "Major" Compaction to LCS
> ------------------------------
>
> Key: CASSANDRA-7272
> URL: https://issues.apache.org/jira/browse/CASSANDRA-7272
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Reporter: T Jake Luciani
> Priority: Minor
> Labels: compaction
> Fix For: 3.0
>
>
> LCS has a number of minor issues (maybe major depending on your perspective).
> LCS is primarily used for wide rows so for instance when you repair data in LCS you end up with a copy of an entire repaired row in L0. Over time if you repair you end up with multiple copies of a row in L0 - L5. This can make predicting disk usage confusing.
> Another issue is cleaning up tombstoned data. If a tombstone lives in level 1 and data for the cell lives in level 5 the data will not be reclaimed from disk until the tombstone reaches level 5.
> I propose we add a "major" compaction for LCS that forces consolidation of data to level 5 to address these.
--
This message was sent by Atlassian JIRA
(v6.2#6252)