[jira] [Commented] (CASSANDRA-5220) Repair improvements when using vnodes

["Yuki Morishita (JIRA)" <ji...@apache.org>]

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

Yuki Morishita commented on CASSANDRA-5220:
-------------------------------------------

I'm inclined to mark this 'later' in favor of incremental repair and internal refactoring such as CASSANDRA-6455.
Especially, incremental repair should decrease the time needed for validating data, which is one of the major heavy-liftin processes of repair.


> Repair improvements when using vnodes
> -------------------------------------
>
>                 Key: CASSANDRA-5220
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-5220
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: 1.2.0 beta 1
>            Reporter: Brandon Williams
>            Assignee: Yuki Morishita
>              Labels: performance, repair
>             Fix For: 3.0
>
>         Attachments: 5220-yourkit.png, 5220-yourkit.tar.bz2
>
>
> Currently when using vnodes, repair takes much longer to complete than without them.  This appears at least in part because it's using a session per range and processing them sequentially.  This generates a lot of log spam with vnodes, and while being gentler and lighter on hard disk deployments, ssd-based deployments would often prefer that repair be as fast as possible.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)