Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Wed, 29 Oct 2014 21:44:33 +0000 (UTC)
From: "sankalp kohli (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12751522.1414618961000.366937.1414619073800@Atlassian.JIRA>
In-Reply-To: <JIRA.12751522.1414618961000@Atlassian.JIRA>
References: <JIRA.12751522.1414618961000@Atlassian.JIRA>
 <JIRA.12751522.1414618961346@arcas>
Subject: [jira] [Commented] (CASSANDRA-8217) Fail snapshot based repair if
 Merkle tree does not use the same snapshot
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

sankalp kohli commented on CASSANDRA-8217:
------------------------------------------

[~yukim]  What do you think? I can fix this. 

> Fail snapshot based repair if Merkle tree does not use the same snapshot
> ------------------------------------------------------------------------
>
>                 Key: CASSANDRA-8217
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-8217
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: sankalp kohli
>            Priority: Minor
>
> Snapshot based repair rely on having a snapshot on each replica. If for some reason, snapshot is not found or is different, we should fail the repair. This will avoid streaming lot of data around.


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