[
https://issues.apache.org/jira/browse/CASSANDRA-7019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14147831#comment-14147831
]
Jeremiah Jordan commented on CASSANDRA-7019:
--------------------------------------------
Since this is going in 3.0, maybe we should make this the "default" nodetool
compact. I don't know of any case where the STCS "put everything in one file"
is really what people want. And for LCS all we used to do is run the
compaction task like normal. If we still want a way to "kick" compaction for
LCS, we could add a new "nodetool checkcompaction" command or something that
just schedules the compaction manager to run (and does that for STCS and LCS).
Doing that is useful when someone changes compaction settings and there are not
currently writes happening to the system, so making it an explicit command
sounds right to me.
> Major tombstone compaction
> --------------------------
>
> 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
>
>
> 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.3.4#6332)
