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 Tue, 04 Aug 2015 10:18:07 GMT


Stefania commented on CASSANDRA-5220:

Thanks for resuming work at such short notice. 

About the dtests, it's a compatibility issue with the python driver. If you have a copy of
the driver git repository then the "cassandra-test" branch should work.

Otherwise unzip the driver zip file bundled with the cassandra source (lib/
and either install this version (python install) or make sure the cassandra folder
is reachable by the dtests, i.e. by putting it in the same directory as the dtests. If using
a local folder you probably also have to uninstall the official driver, if installed at all.

> 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