[ https://issues.apache.org/jira/browse/CASSANDRA-6434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14051487#comment-14051487 ]
Jonathan Ellis commented on CASSANDRA-6434: ------------------------------------------- I'd actually prefer to use actual-repair-time instead of gcgs approximation even for non-incremental repair. The latter means you could cause "reappearing" data if the approximation is too optimistic (which was what Sankalp originally filed this ticket for; I've modified his description). > 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)