[jira] [Updated] (CASSANDRA-7272) Add "Major" Compaction to LCS and split sstables during STCS major compaction

["Jeremiah Jordan (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CASSANDRA-7272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jeremiah Jordan updated CASSANDRA-7272:
---------------------------------------
    Summary: Add "Major" Compaction to LCS and split sstables during STCS major compaction  (was: Add "Major" Compaction to LCS )

> Add "Major" Compaction to LCS and split sstables during STCS major compaction
> -----------------------------------------------------------------------------
>
>                 Key: CASSANDRA-7272
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-7272
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: T Jake Luciani
>            Assignee: Marcus Eriksson
>            Priority: Minor
>              Labels: compaction, docs-impacting, lcs
>             Fix For: 2.2.0 beta 1
>
>
> 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
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org