[
https://issues.apache.org/jira/browse/CASSANDRA-6434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14647402#comment-14647402
]
Marcus Eriksson commented on CASSANDRA-6434:
--------------------------------------------
bq. Couldn't we use a non-optimal (but much simpler and hopefully good enough)
solution for that? Typically, unrepaired sstables should, by design, be fairly
recent. So what if we said that we only purge tombstone if it's older than
gcGrace and its localDeletionTime is older than then oldest localDeletion in
the unrepaired sstables used by the query?
That is a much better idea, first stab at that here:
https://github.com/krummas/cassandra/commits/marcuse/6434-trunk-2
> Repair-aware gc grace period
> -----------------------------
>
> Key: CASSANDRA-6434
> URL: https://issues.apache.org/jira/browse/CASSANDRA-6434
> Project: Cassandra
> Issue Type: New Feature
> Components: Core
> Reporter: sankalp kohli
> Assignee: Marcus Eriksson
> Fix For: 3.0 beta 1
>
>
> Since the reason for gcgs is to ensure that we don't purge tombstones until
> every replica has been notified, it's redundant in a world where we're
> tracking repair times per sstable (and repairing frequentily), i.e., a world
> where we default to incremental repair a la CASSANDRA-5351.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
