[
https://issues.apache.org/jira/browse/CASSANDRA-6434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14051181#comment-14051181
]
Marcus Eriksson commented on CASSANDRA-6434:
--------------------------------------------
Hmm, I guess the only reason to keep gcgs is for people who don't run
incremental repair (with incremental repair we can, as [~kohlisankalp] mentions
above set gcgs to 0 when compacting repaired data).
Since we don't make incremental repairs default until 3.0, we should probably
keep gcgs there for people not using inc repair and then, in 3.1 (or 4.0), both
remove gcgs and make full repairs mark data as repaired.
> 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)
