cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Blake Eggleston (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-10446) Run repair with down replicas
Date Mon, 07 Nov 2016 23:54:58 GMT

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

Blake Eggleston commented on CASSANDRA-10446:
---------------------------------------------

Oh wow, good catch, that's not good. So that issue, and several others, will be addressed
in CASSANDRA-9143. I'm hoping to post a patch for it by the end of this week. Since that should
address the fundamental issue of data being misclassified as repaired I've just pushed a commit
up to my branch that doesn't set repairedAt, or run anti-compaction when the force flag is
set.

> Run repair with down replicas
> -----------------------------
>
>                 Key: CASSANDRA-10446
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-10446
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: sankalp kohli
>            Assignee: Blake Eggleston
>            Priority: Minor
>             Fix For: 4.0
>
>
> We should have an option of running repair when replicas are down. We can call it -force.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message