cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "sankalp kohli (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-7272) Add "Major" Compaction to LCS
Date Sun, 05 Oct 2014 04:05:34 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-7272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14159419#comment-14159419
] 

sankalp kohli commented on CASSANDRA-7272:
------------------------------------------

[~tjake]  I think this is a dupe of CASSANDRA-7019, like you said. Can you close this? 

> 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.3.4#6332)

Mime
View raw message