[
https://issues.apache.org/jira/browse/CASSANDRA-3721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vijay resolved CASSANDRA-3721.
------------------------------
Resolution: Fixed
Sorry for the confusion, +1 for me and i committed it again... I did test it
and unit test passes. Thanks!
> Staggering repair
> -----------------
>
> Key: CASSANDRA-3721
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3721
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Affects Versions: 1.1.0
> Reporter: Vijay
> Assignee: Vijay
> Priority: Minor
> Fix For: 1.1.1
>
> Attachments: 0001-add-snapshot-command.patch,
> 0001-staggering-repair-with-snapshot.patch, 3721.patch
>
>
> Currently repair runs on all the nodes at once and causing the range of data
> to be hot (higher latency on reads).
> Sequence:
> 1) Send a repair request to all of the nodes so we can hold the references of
> the SSTables (point at which repair was initiated)
> 2) Send Validation on one node at a time (once completed will release
> references).
> 3) Hold the reference of the tree in the requesting node and once everything
> is complete start diff.
> We can also serialize the streaming part not more than 1 node is involved in
> the streaming.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
