[
https://issues.apache.org/jira/browse/CASSANDRA-8497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15303883#comment-15303883
]
Marcus Eriksson commented on CASSANDRA-8497:
--------------------------------------------
agreed, even for repaired data we still keep the tombstones around for at least
gcgs
> Do not replay commit log records for tables that have been repaired since
> -------------------------------------------------------------------------
>
> Key: CASSANDRA-8497
> URL: https://issues.apache.org/jira/browse/CASSANDRA-8497
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Benedict
> Priority: Minor
>
> If somehow we have commit log records around since prior to a repair was
> completed, and we have repair-aware tombstone collection, then we could
> potentially reintroduce deleted data. Since we consider repaired data to be
> completely up-to-date, unless there has been a cross-cluster failure where
> data only ended up in the commit log, the commit log records will by now be
> superfluous. Some grace period may be necessary, as with CASSANDRA-6434.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
