cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcus Eriksson (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:45:41 GMT

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

Marcus Eriksson commented on CASSANDRA-13392:
---------------------------------------------

Ok so it is not safe to remove the repair flag and it is not safe to keep it. Maybe we should
just fail the refresh if there is a repaired sstable, forcing the user to either mark it unrepaired
using tools/bin/sstablerepairedset or restarting the node to keep the flag?

> 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