cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nate McCall (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-12709) Nothing logged when lots of expired tombstones in a slice query
Date Mon, 26 Sep 2016 17:31:20 GMT


Nate McCall commented on CASSANDRA-12709:

            // An expired tombstone will be immediately discarded in memory, and needn't be
            // Neither should be any cell shadowed by a range- or a partition tombstone.
            if (cell.getLocalDeletionTime() < gcBefore || !columnCounter.count(cell, tester))

Yeah, that's not cool from an operator's perspective (and actually answers a question or two
I've had recently with tombstone issues on 2.1 and 2.2 clusters). 

This behavior works as one would expect again in 3.x in that if it's a tombstone, we count

A patch will have to include a {{NEWS.txt}} entry as we will be modifying production behavior
and will for sure catch some people unaware. 

> Nothing logged when lots of expired tombstones in a slice query
> ---------------------------------------------------------------
>                 Key: CASSANDRA-12709
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>            Reporter: nicolas ginder
>            Priority: Minor
> Currently Cassandra only logs a warning and an error for non expired tombstones, see
org.apache.cassandra.db.filter.SliceQueryFilter. Expired tombstones used to be included in
the tombstone count but this has been removed by CASSANDRA-9299.
> It is unclear that expired tombstones are not counted anymore, making tombstone_warn_threshold
and tombstone_failure_threshold property names misleading.
> Currently the only way to get some visibility is by running SSTableMetadataViewer to
get the droppable tombstone  ratio.

This message was sent by Atlassian JIRA

View raw message