cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sylvain Lebresne (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-5228) Track maximum ttl and use to expire entire sstables
Date Tue, 12 Mar 2013 16:55:13 GMT


Sylvain Lebresne commented on CASSANDRA-5228:

I suspect we'd rather make that automatic rather a nodetool command if possible. In fact,
we could do that for every compaction. Typically, when we create the compaction iterator,
we could skip sstables that can be dropped fully (but still consider them as compacted).

We may also want to tweak slightly AbstractCompactionStrategy.worthDroppingTombstones so it
return yes if the maxLocalDeletion time is less than gcBefore (though the current version
should work reasonably well already).
> Track maximum ttl and use to expire entire sstables
> ---------------------------------------------------
>                 Key: CASSANDRA-5228
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Jonathan Ellis
>            Assignee: Marcus Eriksson
>            Priority: Minor
>         Attachments: 0001-track-max-local-deletiontime-v2.patch, 0001-track-max-local-deletiontime-v3.patch,
0001-track-max-ttl-v1.patch, 0002-CASSANDRA-5228-add-a-nodetool-command-that-drops-ent.patch
> It would be nice to be able to throw away entire sstables worth of data when we know
that it's all expired.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message