[
https://issues.apache.org/jira/browse/CASSANDRA-12030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Ellis updated CASSANDRA-12030:
---------------------------------------
Fix Version/s: (was: 2.1.16)
I've pulled this out of 2.1.16 after a [dev list
discussion|https://mail-archives.apache.org/mod_mbox/cassandra-dev/201607.mbox/%3CCALdd-zjg%2Ba73VncPkU2rw_UpFPVsw0yNwO-yBqUQfK8H8FpiKw%40mail.gmail.com%3E]
on taking a more rigorous line on our policy of critical fixes only for 2.1.x.
> Range tombstones that are masked by row tombstones should not be written out
> ----------------------------------------------------------------------------
>
> Key: CASSANDRA-12030
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12030
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Nachiket Patil
> Assignee: Nachiket Patil
> Priority: Minor
> Fix For: 2.2.8
>
> Attachments: cassandra-12030-2.1.diff, cassandra-12030-2.2.diff
>
>
> During compaction, if a table has range tombstone and a row delete with
> higher timestamp than range tombstone, both are written out to disk. Some
> problems seen because of this behavior:
> 1. The Range tombstone is expensive to maintain.
> 2. Range queries see timeouts when there are too many range tombstones
> present which may be masked by row tombstones.
> This can be avoided with simple optimization to not write out range tombstone
> if it is masked by row delete.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
