cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sylvain Lebresne (JIRA)" <>
Subject [jira] [Updated] (CASSANDRA-2433) Failed Streams Break Repair
Date Wed, 31 Aug 2011 14:46:10 GMT


Sylvain Lebresne updated CASSANDRA-2433:

    Attachment: 2433_v3.patch

bq. Someone's probably going to want the JMX information but let's keep Stages for Verb-associated

Sounds good, updated patch add a new executor directly into AntiEntropy.

bq. How about splitting onDead and onRestart in EndpointStateChange, then?


bq. I prefer using WrappedRunnable to a Callable

I changed to use WrappedRunnable. However, we still need to have access to both the repair
session and the future from the executor so the implementation returns a pair of those two
objects. I'm only marginally convinced this is cleaner than the previous solution...

> Failed Streams Break Repair
> ---------------------------
>                 Key: CASSANDRA-2433
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>            Reporter: Benjamin Coverston
>            Assignee: Sylvain Lebresne
>              Labels: repair
>             Fix For: 0.8.5
>         Attachments: 0001-Put-repair-session-on-a-Stage-and-add-a-method-to-re-v4.patch,
0002-Register-in-gossip-to-handle-node-failures-v4.patch, 0003-Report-streaming-errors-back-to-repair-v4.patch,
0004-Reports-validation-compaction-errors-back-to-repair-v4.patch, 2433.patch, 2433_v2.patch,
> Running repair in cases where a stream fails we are seeing multiple problems.
> 1. Although retry is initiated and completes, the old stream doesn't seem to clean itself
up and repair hangs.
> 2. The temp files are left behind and multiple failures can end up filling up the data
> These issues together are making repair very difficult for nearly everyone running repair
on a non-trivial sized data set.
> This issue is also being worked on w.r.t CASSANDRA-2088, however that was moved to 0.8
for a few reasons. This ticket is to fix the immediate issues that we are seeing in 0.7.

This message is automatically generated by JIRA.
For more information on JIRA, see:


View raw message