[
https://issues.apache.org/jira/browse/CASSANDRA-5220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcus Olsson updated CASSANDRA-5220:
-------------------------------------
Attachment: cassandra-3.0-5220-2.patch
With this patch the dtest works for me, both with vnodes and without.
There was a problem with wrap around ranges and the merkle tree iterator I made
that only occurred if there was data around both the min and max tokens. The
problem was that it had already iterated over the merkle tree for the wrap
around range in the beginning, so the solution I chose was to reiterate over
the merkle trees in Validator.add() if the end was reached.
With the patch applied I saw a ~4 seconds improvement(from ~18 to ~14) when
using vnodes. Without vnodes it took around 10-11 seconds.
> 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
> 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)
