Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Wed, 20 Jan 2016 07:14:39 +0000 (UTC)
From: "Anuj Wadehra (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12902521.1444081595000.155673.1453274079944@Atlassian.JIRA>
In-Reply-To: <JIRA.12902521.1444081595000@Atlassian.JIRA>
References: <JIRA.12902521.1444081595000@Atlassian.JIRA>
 <JIRA.12902521.1444081595825@arcas>
Subject: [jira] [Commented] (CASSANDRA-10446) Run repair with down replicas
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Anuj Wadehra commented on CASSANDRA-10446:
------------------------------------------

Whether its bug or an improvement is debatable. The intent of the suggestion to increase the priority and change the type was to ensure that it gets due attention. I think by giving detailed scneario, I have tried to explain the critically of the issue. No, I was not interested in working on this.  

> 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
>            Priority: Minor
>             Fix For: 3.x
>
>
> 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)