cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vinay Chella (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-9079) "respectTombstoneThresholds" should be configurable
Date Tue, 31 Mar 2015 21:19:53 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-9079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14389434#comment-14389434
] 

Vinay Chella commented on CASSANDRA-9079:
-----------------------------------------

Yes, that is a good work around and is being done in our clusters. But isn't making "respectTombstoneThresholds"
configurable would be the cleaner approach? I am trying to understand the intricacies of exposing
"SliceQueryFilter.respectTombstoneThresholds()" to be configurable.



> "respectTombstoneThresholds" should be configurable 
> ----------------------------------------------------
>
>                 Key: CASSANDRA-9079
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-9079
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Vinay Chella
>              Labels: tombstone
>         Attachments: 9079.txt
>
>
> Currently there is no way to control/ configure the functionality of "drop queries exceeding
a configurable number of tombstones". Making this functionality configurable through yaml
helps use case like:
> We have several production clusters with large number of tombstones due to aggressive
TTLs with very small payloads, and low gc_grace_seconds. Most of the read queries on these
column families are ending up in drop operations or excessive warn messages due to "tombstone_failure_threshold"
and "tombstone_warn_threshold". One cannot deterministically disable these tombstone thresholds
by setting high values. Hence, making "SliceQueryFilter.respectTombstoneThresholds()" configurable
through yaml would be the better approach. 
> Column families with small payloads (couple hundred bytes) having large number of tombstones
would not lead to "Avoid death-by-tombstone by default (CASSANDRA-6117)", which is the reason
for observed drop operations. We see drop operations before compactions catch up, and clean
those tombstones with both STCS and LCS. Configurable "respectTombstoneThresholds()" will
help in reducing tombstone warnings noise.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message