[
https://issues.apache.org/jira/browse/CASSANDRA-2610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13095916#comment-13095916
]
Hudson commented on CASSANDRA-2610:
-----------------------------------
Integrated in Cassandra #1067 (See
[https://builds.apache.org/job/Cassandra/1067/])
Make repair of a range sync all replica pairs for this range
patch by slebresne; reviewed by jbellis for CASSANDRA-2610
slebresne :
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1164463
Files :
* /cassandra/trunk/CHANGES.txt
* /cassandra/trunk/src/java/org/apache/cassandra/net/MessagingService.java
* /cassandra/trunk/src/java/org/apache/cassandra/service/AntiEntropyService.java
* /cassandra/trunk/src/java/org/apache/cassandra/service/StorageService.java
*
/cassandra/trunk/src/java/org/apache/cassandra/streaming/StreamingRepairTask.java
* /cassandra/trunk/src/java/org/apache/cassandra/utils/UUIDGen.java
* /cassandra/trunk/test/unit/org/apache/cassandra/io/CompactSerializerTest.java
*
/cassandra/trunk/test/unit/org/apache/cassandra/service/AntiEntropyServiceTestAbstract.java
> 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: 1.0
>
> Attachments: 0001-Make-repair-repair-all-hosts-v2.patch,
> 0001-Make-repair-repair-all-hosts.patch, 0002-Cleanup-log-messages-v2.patch,
> 0003-cleanup-and-fix-private-reference.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 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
