[
https://issues.apache.org/jira/browse/CASSANDRA-3112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sylvain Lebresne updated CASSANDRA-3112:
----------------------------------------
Attachment:
0004-Reports-validation-compaction-errors-back-to-repair-v4.patch
0003-Report-streaming-errors-back-to-repair-v4.patch
Attaching the 2 last patches from an initial version of CASSANDRA-2433 that
were handling this. This will need to be rebased to current code though.
> 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: 1.1
>
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
