cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-2305) Tombstoned rows not purged from cache after gcgraceseconds
Date Sun, 10 Apr 2011 19:08:05 GMT


Hudson commented on CASSANDRA-2305:

Integrated in Cassandra-0.7 #429 (See [])
    Purge tombstone from row cache (0.7 version)
patch by slebresne; reviewed by jbellis for CASSANDRA-2305

> Tombstoned rows not purged from cache after gcgraceseconds
> ----------------------------------------------------------
>                 Key: CASSANDRA-2305
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 0.7.0
>            Reporter: Jeffrey Wang
>            Assignee: Sylvain Lebresne
>            Priority: Minor
>             Fix For: 0.7.5
>         Attachments: 0001-Compaction-test.patch, 0002-Invalidate-row-cache-on-compaction-purge.patch,
>   Original Estimate: 2h
>          Time Spent: 2h
>  Remaining Estimate: 0h
> From email to list:
> I was wondering if this is the expected behavior of deletes (0.7.0). Let's say I have
a 1-node cluster with a single CF which has gc_grace_seconds = 0. The following sequence of
operations happens (in the given order):
> insert row X with timestamp T
> delete row X with timestamp T+1
> force flush + compaction
> insert row X with timestamp T
> My understanding is that the tombstone created by the delete (and row X) will disappear
with the flush + compaction which means the last insertion should show up. My experimentation,
however, suggests otherwise (the last insertion does not show up).
> I believe I have traced this to the fact that the markedForDeleteAt field on the ColumnFamily
does not get reset after a compaction (after gc_grace_seconds has passed); is this desirable?
I think it introduces an inconsistency in how tombstoned columns work versus tombstoned CFs.

This message is automatically generated by JIRA.
For more information on JIRA, see:

View raw message