cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aleksey Yeschenko (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-9326) Seeing tombstone warning message
Date Thu, 07 May 2015 19:57:00 GMT


Aleksey Yeschenko commented on CASSANDRA-9326:

{{localDeletion=2147483647}} ({{Integer.MAX_VALUE}}) here only means that there is no partition
level deletion here.

The reasons you see that warning are that 1) compaction hasn't yet compacted them all away
and 2) the way the column counter works. CASSANDRA-9326 is open to handle the latter, and
you'll have to deal with the former.

> Seeing tombstone warning message
> --------------------------------
>                 Key: CASSANDRA-9326
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>            Reporter: srinivasu gottipati
>            Priority: Minor
>             Fix For: 2.0.x
> We deleted data for some of the rows in one of the column families. 
> After that we ran repair on all nodes, and followed by reducing gc_grace_seconds that
way compaction can remove all the tombstones upon expiry of gc_grace_seconds time. 
> When we are querying the data now, seeing the following errors:
> WARN [ReadStage:1142] 2015-05-06 17:50:53,602 (line 231) Read 1
live and 1487 tombstoned cells in XXXX (see tombstone_warn_threshold). 10001 columns was requested,
slices=[-], delInfo={deletedAt=-9223372036854775808, localDeletion=2147483647} 
> We deleted this data while back and for sure gc_grace_seconds is elapsed long time back
and we use leveled compaction. In the above, errors, localDeletion points to some time in
future (MAX INT VALUE) and that could be the reason these are n't being purged. Any help (or)
workaround is appreciated.

This message was sent by Atlassian JIRA

View raw message