cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeremiah Jordan (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (CASSANDRA-6042) Add WARN when there are a lot of tombstones in a query
Date Wed, 18 Sep 2013 20:57:52 GMT

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

Jeremiah Jordan edited comment on CASSANDRA-6042 at 9/18/13 8:57 PM:
---------------------------------------------------------------------

I still think it is useful to have this, unless CASSANDRA-6057 is going to tell me the offending
row key.  This is helping for the case of "I know I have a tombstone issue, wtf row is it
in?".  Also I have no problem making it painful for people who do this knowing they are "doing
it wrong", to give a nudge to people who don't realize they are "doing it wrong".
                
      was (Author: jjordan):
    I still think it is useful to have this, unless CASSANDRA-6057 is going to tell me the
offending row key.  This is helping for the case of "I know I have a tombstone issue, wtf
row is it in?"
                  
> 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: Lyuben Todorov
>            Priority: Minor
>             Fix For: 1.2.10
>
>
> 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

Mime
View raw message