Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Tue, 31 Mar 2015 18:26:53 +0000 (UTC)
From: "Vinay Chella (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12787107.1427826122000.84051.1427826413061@Atlassian.JIRA>
In-Reply-To: <JIRA.12787107.1427826122000@Atlassian.JIRA>
References: <JIRA.12787107.1427826122000@Atlassian.JIRA>
 <JIRA.12787107.1427826122355@arcas>
Subject: [jira] [Updated] (CASSANDRA-9079) "respectTombstoneThresholds"
 should be configurable
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Vinay Chella updated CASSANDRA-9079:
------------------------------------
    Attachment: 9079.txt

Patch

> "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
>             Fix For: 2.0.14
>
>         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)