cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "nicolas ginder (JIRA)" <j...@apache.org>
Subject [jira] [Created] (CASSANDRA-12709) Nothing logged when lots of expired tombstones in a slice query
Date Mon, 26 Sep 2016 13:43:20 GMT
nicolas ginder created CASSANDRA-12709:
------------------------------------------

             Summary: 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
             Fix For: 2.1.x, 2.2.x


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)

Mime
View raw message