[
https://issues.apache.org/jira/browse/CASSANDRA-13392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15948837#comment-15948837
]
Marcus Eriksson commented on CASSANDRA-13392:
---------------------------------------------
Well, if we are running nodetool refresh, we will want the data to reappear on
replicas right? Someone copies in a bunch of sstables on one node, runs repair,
that data should end up on all nodes right?
We will not be moving data from repaired to unrepaired on any 'live' sstables
on the node we are running refresh - only on the sstables copied in to the data
directory. Or do you have some other use case where this is not true?
> 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)
