[
https://issues.apache.org/jira/browse/CASSANDRA-6117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Ellis updated CASSANDRA-6117:
--------------------------------------
Attachment: 6117-v2.txt
v2 splits it into warn at 10k and fail at 50k. That should be ample warning
for a growing tombstone corpus to be dealt with (or the fail threshold
adjusted).
> Avoid death-by-tombstone by default
> -----------------------------------
>
> Key: CASSANDRA-6117
> URL: https://issues.apache.org/jira/browse/CASSANDRA-6117
> Project: Cassandra
> Issue Type: New Feature
> Components: Core
> Reporter: Jonathan Ellis
> Assignee: Jonathan Ellis
> Fix For: 2.0.2
>
> Attachments: 6117.txt, 6117-v2.txt
>
>
> We added warnings to 1.2 (CASSANDRA-6042); for 2.0 we should go farther and
> drop requests (with an error logged) that exceed the threshold. Users who
> want to tread dangerously are free to crank the threshold up, but "I queried
> a lot of tombstones and Cassandra fell over" is possibly the number one way
> of killing Cassandra nodes right now.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
