[
https://issues.apache.org/jira/browse/CASSANDRA-6434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Ellis updated CASSANDRA-6434:
--------------------------------------
Description:
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.
was:
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.
Priority: Major (was: Minor)
Assignee: Marcus Eriksson
Summary: Repair-aware gc grace period (was: Repair aware gc grace
period )
> 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
>
> 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)
