cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sylvain Lebresne (JIRA)" <j...@apache.org>
Subject [jira] [Created] (CASSANDRA-2610) Have the repair of a range repair *all* the replica for that range
Date Thu, 05 May 2011 11:08:03 GMT
Have the repair of a range repair *all* the replica for that range
------------------------------------------------------------------

                 Key: CASSANDRA-2610
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2610
             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


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
annoying).

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: http://www.atlassian.com/software/jira

Mime
View raw message