You are viewing a plain text version of this content. The canonical link for it is here.

Posted to user@cassandra.apache.org by Joel Samuelsson <sa...@gmail.com> on 2014/05/15 10:43:42 UTC

Tombstones on secondary indexes

My system log is full of messages like this one:

WARN [ReadStage:42] 2014-05-15 08:19:13,615 SliceQueryFilter.java (line
210) Read 0 live and 2829 tombstoned cells in
TrafficServer.rawData.rawData_evaluated_idx (see tombstone_warn_threshold)

I've run a major compaction but the tombstones are not removed.

https://issues.apache.org/jira/browse/CASSANDRA-4314 seems to say that
tombstones on secondary indexes are not removed by a compaction. Do I need
to do it manually?

Best regards,
Joel Samuelsson

Re: Tombstones on secondary indexes

Posted by Robert Coli <rc...@eventbrite.com>.

On Thu, May 15, 2014 at 1:43 AM, Joel Samuelsson
<sa...@gmail.com>wrote:

> https://issues.apache.org/jira/browse/CASSANDRA-4314 seems to say that
> tombstones on secondary indexes are not removed by a compaction. Do I need
> to do it manually?
>

The ticket you have pasted says :

"It's not exposed through nodetool, but you can invoke forceMajorCompaction
on the index cfs mbean directly (o.a.c.db.IndexColumnFamilies), or you can
drop and recreate the index."

I would probably suggest the former technique, not the latter.

=Rob