cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefania (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-5220) Repair improvements when using vnodes
Date Mon, 03 Aug 2015 09:25:07 GMT


Stefania commented on CASSANDRA-5220:

I've rebased _cassandra-3.0-5220-2.patch_ on to the latest trunk [here|].

I haven't had the time to look at the code in depth yet, I plan to do so in the next few days.

Meanwhile, these unit tests are failing:

* MerkelTreesTest.testHashRandom
* LeveledCompactionStrategyTest.testValidationMultipleSSTablePerLevel

Initially I though it was because of the rebase but when I applied the patch onto trunk as
of April 2015 [here|], with no conflicts,
they were also failing.

There may be more broken unit tests, I've only checked the ones that were modified by the
patch. Eventually the full CI will appear here:

> Repair improvements when using vnodes
> -------------------------------------
>                 Key: CASSANDRA-5220
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: 1.2.0 beta 1
>            Reporter: Brandon Williams
>            Assignee: Marcus Olsson
>              Labels: performance, repair
>         Attachments: 5220-yourkit.png, 5220-yourkit.tar.bz2, cassandra-3.0-5220-1.patch,
cassandra-3.0-5220-2.patch, cassandra-3.0-5220.patch
> 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

View raw message