[jira] [Commented] (CASSANDRA-3721) Staggering repair

["Sylvain Lebresne (Commented) (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CASSANDRA-3721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13208268#comment-13208268 ] 

Sylvain Lebresne commented on CASSANDRA-3721:
---------------------------------------------

I think there have been a misunderstanding. I've attached 3721.patch that was addressing my concerns with the initial 0001-staggering-repair-with-snapshot.patch. I'm personally good with 3721.patch (It may be that my poor wording suggested otherwise, sorry if that's the case), except that it needs review of course.

Vijay did commit 3721.patch, so I think that was right (though maybe Vijay you could have made it more clear in your comment that you did review the last version, +1ed it and thus committed it). 
                
> 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