cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Juho Mäkinen (JIRA) <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-5220) Repair improvements when using vnodes
Date Thu, 22 May 2014 11:58:03 GMT

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

Juho Mäkinen commented on CASSANDRA-5220:
-----------------------------------------

In addition the repair operation gives poor status on its progress so it would be nice that
some additional logging about repair progress would be added both to log4j and also to JMX.

> 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: 2.1.1
>
>         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.2#6252)

Mime
View raw message