[
https://issues.apache.org/jira/browse/CASSANDRA-7019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcus Eriksson updated CASSANDRA-7019:
---------------------------------------
Description:
When there are no other compactions to do, we trigger a single-sstable
compaction if there is more than X% droppable tombstones in the sstable.
In this ticket we should try to include overlapping sstables in those
compactions to be able to actually drop the tombstones. Might only be doable
with LCS (with STCS we would probably end up including all sstables)
was:
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.
> Improve tombstone compactions
> -----------------------------
>
> Key: CASSANDRA-7019
> URL: https://issues.apache.org/jira/browse/CASSANDRA-7019
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Marcus Eriksson
> Assignee: Marcus Eriksson
> Labels: compaction
> Fix For: 3.0
>
>
> When there are no other compactions to do, we trigger a single-sstable
> compaction if there is more than X% droppable tombstones in the sstable.
> In this ticket we should try to include overlapping sstables in those
> compactions to be able to actually drop the tombstones. Might only be doable
> with LCS (with STCS we would probably end up including all sstables)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
