[
https://issues.apache.org/jira/browse/CASSANDRA-6042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13774114#comment-13774114
]
Russell Alexander Spitzer commented on CASSANDRA-6042:
------------------------------------------------------
Thanks! I hoped that I had everything in the right place but it is a bit hard
to keep the names/read_paths straight in my head. This was a great ticket to
start diving into the read path though.
Attached revised patch.
> 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
>
> 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
