You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Alexey Plotnik (JIRA)" <ji...@apache.org> on 2014/07/15 00:46:06 UTC

[jira] [Commented] (CASSANDRA-7019) Major tombstone compaction

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

Alexey Plotnik commented on CASSANDRA-7019:
-------------------------------------------

That's what we needed. We have LCS and a lot of SSTables. Compaction process always retain a lot of tombstones. We need something like super-compaction, or tombstone-compaction, or name it as you want. There is must be a procedure similar Cleanup, but for tombstones deletions. I like it.

> Major tombstone compaction
> --------------------------
>
>                 Key: CASSANDRA-7019
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-7019
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Marcus Eriksson
>              Labels: compaction
>
> It should be possible to do a "major" tombstone compaction by including all sstables, but writing them out 1:1, meaning that if you have 10 sstables before, you will have 10 sstables after the compaction with the same data, minus all the expired tombstones.
> We could do this in two ways:
> # a nodetool command that includes _all_ sstables
> # once we detect that an sstable has more than x% (20%?) expired tombstones, we start one of these compactions, and include all overlapping sstables that contain older data.



--
This message was sent by Atlassian JIRA
(v6.2#6252)