[
https://issues.apache.org/jira/browse/CASSANDRA-5220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14653407#comment-14653407
]
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/cassandra-driver-internal-only-2.6.0c2.zip) and either install this
version (python setup.py 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: 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)
