Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Thu, 27 Mar 2014 20:47:17 +0000 (UTC)
From: "Ryan McGuire (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12630778.1360019633971.19502.1395953237947@arcas>
In-Reply-To: <JIRA.12630778.1360019633971@arcas>
References: <JIRA.12630778.1360019633971@arcas>
Subject: [jira] [Commented] (CASSANDRA-5220) Repair improvements when using
 vnodes
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Ryan McGuire commented on CASSANDRA-5220:
-----------------------------------------

As of today, on cassandra-2.0 HEAD

repair_test.TestRepair.simple_repair_test:

bq.    without vnodes: Repair time: 5.10s
bq.    with vnodes: Repair time: 562.97s

100x slower than without vnodes. So I'm not sure what happened here since @driftx ran this in November.

> 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
>             Fix For: 2.1 beta2
>
>
> 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)