[
https://issues.apache.org/jira/browse/CASSANDRA-6434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13884358#comment-13884358
]
sankalp kohli commented on CASSANDRA-6434:
------------------------------------------
Once CASSANDRA-5351 is fixed, I think we can drop tombstones of repaired
stables if the original data has been compacted. We don't need to keep track of
last repair time.
> 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
> Priority: Minor
>
> If we don't run repair every gc grace period, forgotten delete problem can
> happen. This can be very bad for some use cases.
> To avoid this, the only way is to guaranty that we run repair successfully
> across the cluster every gc grace period.
> This is operationally very hard to achieve when we are dealing with lot of
> nodes.
> Also repair can fail for many reasons like machine failures, one stable which
> is bad, etc.
> So one solution to this is to add a new optional feature(disable by default)
> which only delete tombstones if repair has successfully run on it instead of
> relying on gc grace period. We can track the last successful repair time in a
> system key space.
> This feature will be very useful for use cases which cannot tolerate data
> reappearing.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
