[
https://issues.apache.org/jira/browse/CASSANDRA-5745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13705823#comment-13705823
]
Jonathan Ellis commented on CASSANDRA-5745:
-------------------------------------------
bq. include all (possibly several thousand) sstables in a single compaction to
the highest level, could be dangerous since we might OOM (see the comment
around MAX_COMPACTING_L0 in LeveledManifest for example).
We could restrict it to "Everything in L1+," which would allow us to use the
"one sstable at a time, per level" iterator.
bq. The newly flushed data would quickly trickle up through the empty levels
and then get compacted with all the max-level sstables.
You're right, I don't think it works.
> Minor compaction tombstone-removal deadlock
> -------------------------------------------
>
> Key: CASSANDRA-5745
> URL: https://issues.apache.org/jira/browse/CASSANDRA-5745
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Reporter: Jonathan Ellis
> Fix For: 2.0.1
>
>
> From a discussion with Axel Liljencrantz,
> If you have two SSTables that have temporally overlapping data, you can get
> lodged into a state where a compaction of SSTable A can't drop tombstones
> because SSTable B contains older data *and vice versa*. Once that's happened,
> Cassandra should be wedged into a state where CASSANDRA-4671 no longer helps
> with tombstone removal. The only way to break the wedge would be to perform a
> compaction containing both SSTable A and SSTable B.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
