cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CASSANDRA-9326) Seeing tombstone warning message
Date Tue, 25 Aug 2015 04:15:47 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-9326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jonathan Ellis resolved CASSANDRA-9326.
---------------------------------------
       Resolution: Won't Fix
    Fix Version/s:     (was: 2.0.x)

Closing out 2.0.  Improvements are on the roadmap for future versions as noted above.

> Seeing tombstone warning message
> --------------------------------
>
>                 Key: CASSANDRA-9326
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-9326
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>            Reporter: srinivasu gottipati
>            Priority: Minor
>
> 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 SliceQueryFilter.java (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
(v6.3.4#6332)

Mime
View raw message