cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefan Podkowinski (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-13392) Repaired status should be cleared on new sstables when issuing nodetool refresh
Date Thu, 30 Mar 2017 11:38:41 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-13392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15948896#comment-15948896
] 

Stefan Podkowinski commented on CASSANDRA-13392:
------------------------------------------------

Let's say one of my sstables got corrupted and removed/scrubbed manually afterwards. Node
has been started again. Now the admin pulls the same sstable from yesterdays backup into the
data dir and runs refresh. Having the "new" sstable replicated during next repair would be
rather unexpected and not safe. 

> 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)

Mime
View raw message