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:57:41 GMT

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

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

bq. 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?

Shouldn't you use sstableloader in that case? I personally would never thought of using nodetool
refresh for this. For me it's simply a command to make copied sstables available in a running
Cassandra process. I also don't understand why it should make a difference here running refresh
or restarting the node. How would users know in which case to refresh or restart?



> 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