cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sylvain Lebresne (JIRA)" <>
Subject [jira] [Updated] (CASSANDRA-2610) Have the repair of a range repair *all* the replica for that range
Date Tue, 17 May 2011 20:05:47 GMT


Sylvain Lebresne updated CASSANDRA-2610:

    Attachment: 0001-Make-repair-repair-all-hosts.patch

Patch against 0.8.1. It applies on top of CASSANDRA-2433 because it is changing enough of
common code that I don't want to have to deal with the rebase back and forth (and it actually
reuse some of the refactoring of CASSANDRA-2433 anyway)

> Have the repair of a range repair *all* the replica for that range
> ------------------------------------------------------------------
>                 Key: CASSANDRA-2610
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: 0.8 beta 1
>            Reporter: Sylvain Lebresne
>            Assignee: Sylvain Lebresne
>            Priority: Minor
>             Fix For: 0.8.1
>         Attachments: 0001-Make-repair-repair-all-hosts.patch
>   Original Estimate: 8h
>  Remaining Estimate: 8h
> Say you have a range R whose replica for that range are A, B and C. If you run repair
on node A for that range R, when the repair end you only know that A is fully repaired. B
and C are not. That is B and C are up to date with A before the repair, but are not up to
date with one another.
> It makes it a pain to schedule "optimal" cluster repairs, that is repairing a full cluster
without doing work twice (because you would have still have to run a repair on B or C, which
will make A, B and C redo a validation compaction on R, and with more replica it's even more
> However it is fairly easy during the first repair on A to have him compare all the merkle
trees, i.e the ones for B and C, and ask to B or C to stream between them whichever the differences
they have. 

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

View raw message