[
https://issues.apache.org/jira/browse/CASSANDRA-6434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14070370#comment-14070370
]
Jonathan Ellis commented on CASSANDRA-6434:
-------------------------------------------
bq. I don't think that would work since max(repairtime) is dependent on
compaction
Actually we don't really care *when* it was repaired; as long as it *has* been
repaired. So really the logic should be, "if I'm compacting a repaired
sstable, and it doesn't shadow any data in other sstables, then I can drop the
ts immediately."
bq. Lets use gcgs on unrepaired data until we always mark sstables as repaired.
I suppose we could do that, but the alternative of "don't drop tombstones at
all until it's repaired" is more technically correct.
> 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
>
>
> 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.2#6252)
