cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Oleg Anastasyev (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-6117) Avoid death-by-tombstone by default
Date Wed, 02 Oct 2013 15:36:42 GMT

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

Oleg Anastasyev commented on CASSANDRA-6117:
--------------------------------------------

Guys, I see a lot of log messages like
{code}
 WARN [CompactionExecutor:158] SliceQueryFilter - Read 1 live and 1123 tombstoned cells (see
tombstone_warn_threshold)
{code}
on compaction of normal CF. 
IMHO reading a lot of thombstones on compaction and GC them is normal and should not be warned
(nor failed with TombstoneOverwhelmingException)

> 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, 6117-v3.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)

Mime
View raw message