[
https://issues.apache.org/jira/browse/CASSANDRA-13392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15948820#comment-15948820
]
Stefan Podkowinski commented on CASSANDRA-13392:
------------------------------------------------
How would the repairedAt flag be set, if the sstables haven't been repaired
before? Moving sstables from repaired to unrepaired again can resurrect data
that has already been purged from the replicas, so it's not safe to assume that
we can always drop sstables to unrepaired without consistency implications.
> Repaired status should be cleared on new sstables when issuing nodetool
> refresh
> -------------------------------------------------------------------------------
>
> Key: CASSANDRA-13392
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13392
> Project: Cassandra
> Issue Type: Bug
> Reporter: Marcus Eriksson
> Assignee: Marcus Eriksson
> Fix For: 3.0.x, 3.11.x, 4.x
>
>
> We can't assume that new sstables added when doing nodetool refresh
> (ColumnFamilyStore#loadNewSSTables) are actually repaired if they have the
> repairedAt flag set
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
