You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Takenori Sato (JIRA)" <ji...@apache.org> on 2014/10/02 03:44:34 UTC
[jira] [Created] (CASSANDRA-8038) A new config option to ignore
column tombstones for RR or not
Takenori Sato created CASSANDRA-8038:
----------------------------------------
Summary: A new config option to ignore column tombstones for RR or not
Key: CASSANDRA-8038
URL: https://issues.apache.org/jira/browse/CASSANDRA-8038
Project: Cassandra
Issue Type: New Feature
Reporter: Takenori Sato
CASSANDRA-6117 addressed the death of Cassandra by column tombstones, and whose fix was to raise an error when reading more tombstones than a threshold. I think it is an emergency action, rather than a fix.
We have had this issue for long. So I wondered, in the first place, if it is really necessary to collect non-gc-able tombstones, which could cause concurrent mode failures, and OOM eventually?
Actually, I was surprised by the fact that Cassandra takes them into consideration. Rather, I prefer to raise a threshold, and tell Cassandra to ignore tombstones for digest calculation of RR because a repair is running regularly.
I guess there are some people like me, but not all. So what about adding a new configuration option if Cassandra ignores column tombstones for RR or not?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)