[
https://issues.apache.org/jira/browse/CASSANDRA-5220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brandon Williams reopened CASSANDRA-5220:
-----------------------------------------
Assignee: Yuki Morishita
I think this is still worth looking at.
Without vnodes:
repair_test.TestRepair.simple_repair_test: 103.3584
With vnodes:
repair_test.TestRepair.simple_repair_test: 348.8908
So we're 3-3.5x slower in the simple case. I'll admit that doing the order
preserving repair test with vnodes is whack, but that one takes 10x longer with
vnodes.
> 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
>
>
> 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.1#6144)
