[
https://issues.apache.org/jira/browse/CASSANDRA-12709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nate McCall updated CASSANDRA-12709:
------------------------------------
Fix Version/s: (was: 2.2.x)
(was: 2.1.x)
> Nothing logged when lots of expired tombstones in a slice query
> ---------------------------------------------------------------
>
> Key: CASSANDRA-12709
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12709
> 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
(v6.3.4#6332)
