cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Whang (JIRA)" <>
Subject [jira] [Comment Edited] (CASSANDRA-13561) Purge TTL on expiration
Date Fri, 10 Nov 2017 02:17:00 GMT


Andrew Whang edited comment on CASSANDRA-13561 at 11/10/17 2:16 AM:

CASSANDRA-13643 seems to do something similar, but safer. I think we can close this out.

was (Author: whangsf):
CASSANDRA-13643 seems to do something similar, but safer. Closing this out.

> Purge TTL on expiration
> -----------------------
>                 Key: CASSANDRA-13561
>                 URL:
>             Project: Cassandra
>          Issue Type: New Feature
>            Reporter: Andrew Whang
>            Assignee: Andrew Whang
>            Priority: Minor
>             Fix For: 4.0
> Tables with mostly TTL columns tend to suffer from high droppable tombstone ratio, which
results in higher read latency, cpu utilization, and disk usage. Expired TTL data become tombstones,
and the nature of purging tombstones during compaction (due to checking for overlapping SSTables)
make them susceptible to surviving much longer than expected. A table option to purge TTL
on expiration would address this issue, by preventing them from becoming tombstones. A boolean
purge_ttl_on_expiration table setting would allow users to easily turn the feature on or off.

> Being more aggressive with gc_grace could also address the problem of long lasting tombstones,
but that would affect tombstones from deletes as well. 
> Even if a purged [expired] cell is revived via repair from a node that hasn't yet compacted
away the cell, it would be revived as an expiring cell with the same localDeletionTime, so
reads should properly handle them. As well, it would be purged in the next compaction. 

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message