C. Scott Andreas updated CASSANDRA-5745:
    Component/s: Compaction

> Minor compaction tombstone-removal deadlock
> -------------------------------------------
>                 Key: CASSANDRA-5745
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-5745
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Compaction
>            Reporter: Jonathan Ellis
>            Priority: Minor
>             Fix For: 4.x
> 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 was sent by Atlassian JIRA

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

Reply via email to