cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sylvain Lebresne (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CASSANDRA-12030) Range tombstones that are masked by row tombstones should not be written out
Date Wed, 06 Jul 2016 12:44:11 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-12030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Sylvain Lebresne resolved CASSANDRA-12030.
------------------------------------------
       Resolution: Fixed
    Fix Version/s: 2.2.8
                   2.1.16

I can buy that range tombstone are painful enough in 2.1/2.2 that it's worth alieviating some
of the pain given this is pretty simple. I've run CI on the patch below to be sure, but as
there doesn't seem to be new failures, committed, thanks.

| [12030-2.1|https://github.com/pcmanus/cassandra/commits/12030-2.1] | [utests|http://cassci.datastax.com/job/pcmanus-12030-2.1-testall]
| [dtests|http://cassci.datastax.com/job/pcmanus-12030-2.1-dtest] |
| [12030-2.2|https://github.com/pcmanus/cassandra/commits/12030-2.2] | [utests|http://cassci.datastax.com/job/pcmanus-12030-2.2-testall]
| [dtests|http://cassci.datastax.com/job/pcmanus-12030-2.2-dtest] |


> 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.1.16, 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)

Mime
View raw message