Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Tue, 28 May 2013 22:42:21 +0000 (UTC)
From: "Jonathan Ellis (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12520941.1314808377936.32015.1369780941650@arcas>
In-Reply-To: <JIRA.12520941.1314808377936@arcas>
References: <JIRA.12520941.1314808377936@arcas>
Subject: [jira] [Commented] (CASSANDRA-3112) Make repair fail when an
 unexpected error occurs
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Jonathan Ellis commented on CASSANDRA-3112:
-------------------------------------------

What is the scope of this ticket?  Should it be wontfixed or moved to 2.1?
                
> Make repair fail when an unexpected error occurs
> ------------------------------------------------
>
>                 Key: CASSANDRA-3112
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-3112
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>            Reporter: Sylvain Lebresne
>            Assignee: Sylvain Lebresne
>            Priority: Minor
>              Labels: repair
>             Fix For: 2.0
>
>         Attachments: 0003-Report-streaming-errors-back-to-repair-v4.patch, 0004-Reports-validation-compaction-errors-back-to-repair-v4.patch
>
>
> CASSANDRA-2433 makes it so that nodetool repair will fail if a node participating to repair dies before completing his part of the repair. This handles most of the situation where repair was previously hanging, but repair can still hang if an unexpected error occurs during either the merkle tree creation (an on-disk corruption triggers an IOError say) or during streaming (though I'm not sure what could make streaming failed outside of 'one of the node died' (besides a bug)).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira