Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Mon, 23 Sep 2013 17:53:04 +0000 (UTC)
From: "Jeremiah Jordan (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12669047.1379436718201.4017.1379958784193@arcas>
In-Reply-To: <JIRA.12669047.1379436718201@arcas>
References: <JIRA.12669047.1379436718201@arcas>
Subject: [jira] [Commented] (CASSANDRA-6042) Add WARN when there are a lot
 of tombstones in a query
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Jeremiah Jordan commented on CASSANDRA-6042:
--------------------------------------------

[~jbellis] beat me to it, but LGTM. +1 :).
                
> Add WARN when there are a lot of tombstones in a query
> ------------------------------------------------------
>
>                 Key: CASSANDRA-6042
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-6042
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Jeremiah Jordan
>            Assignee: Russell Alexander Spitzer
>            Priority: Minor
>             Fix For: 1.2.11, 2.0.2
>
>         Attachments: 0001-JMX-and-Debug-Messages-for-Max-Tombstone-Scans.patch, 0002-JMX-and-Debug-Messages-for-Max-Tombstone-Scans.patch
>
>
> Now that we count the number of tombstones hit (so it can go in tracing), can we pick some threshold (or make it configurable with 0 being don't warn), and spit out a warning saying "Just went through 10000 tombstones in partition XYZ".
> Right now if you are having GC problems because some row got a bunch of tombstones, you can turn on server side tracing, and hope the bad query gets in there, or you can keep making heap dumps, dig through them, and hope you catch the query in there.
> I have seen code problems at multiple places causing this same issue (some code causing way more tombstones than it should, for just one row).  And it is a PITA+Luck to debug it right now.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira