[
https://issues.apache.org/jira/browse/CASSANDRA-5220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14653834#comment-14653834
]
Marcus Olsson commented on CASSANDRA-5220:
------------------------------------------
Thanks, I've managed to get the dtests up and running now!
I had some problem running the dtests, but I think there might have been two
small misses with the rebase. So the dtests are now working properly with
[this|https://github.com/emolsson/cassandra/commits/5220] patch and when running
{noformat}
PRINT_DEBUG=True nosetests -s -v
repair_test.py:TestRepair.simple_parallel_repair_test
{noformat}
on both trunk and the patched trunk I see an improvement from ~14.2s to ~6.7s
repair time, and without vnodes(but with the patch) it was ~2s.
> 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: 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
(v6.3.4#6332)
