cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aleksey Yeschenko (JIRA)" <>
Subject [jira] [Updated] (CASSANDRA-9327) Tombstones are not being cleared up
Date Thu, 04 Jun 2015 17:22:40 GMT


Aleksey Yeschenko updated CASSANDRA-9327:
    Fix Version/s:     (was: 2.0.x)

> Tombstones are not being cleared up
> -----------------------------------
>                 Key: CASSANDRA-9327
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: srinivasu gottipati
>            Priority: Critical
> We deleted part of data from one of column families. After that we ran repair, followed
by reducing gc_grace_seconds to have tombstones space to be reclaimed. After this, we kept
the compaction enabled to reclaim this space upon passing gc_grace_seconds. We have done this
while back and for sure gc_grace_seconds has elapsed.
> Currently, when we run queries against this column family, we are seeing lot of tombstone
errors like below:
> WARN [ReadStage:1113] 2015-05-06 17:48:22,556 (line 231) Read 19
live and 1140 tombstoned cells in YYY (see tombstone_warn_threshold). 10001 columns was requested,
slices=[-], delInfo={deletedAt=-9223372036854775808, localDeletion=2147483647} 
> The localDeletion reported above is time in future (year:2038, I believe it is the default
Integer.MAX_VALUE), and I believe this could be the reason it is not being reclaimed.
> May I know, how do we purge this tombstones and also, what could have set this date to
time in future?

This message was sent by Atlassian JIRA

View raw message