cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brandon Williams (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-6042) Add WARN when there are a lot of tombstones in a query
Date Thu, 19 Sep 2013 00:44:52 GMT


Brandon Williams commented on CASSANDRA-6042:

Totally fine with DEBUG.  The problem with having it enabled by default is, if someone is
doing this purposefully and then upgrade, suddenly logging is going to consume a large portion
of the CPU and tank their cluster.
> Add WARN when there are a lot of tombstones in a query
> ------------------------------------------------------
>                 Key: CASSANDRA-6042
>                 URL:
>             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:

View raw message