[ 
https://issues.apache.org/jira/browse/CASSANDRA-5220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14653376#comment-14653376
 ] 

Marcus Olsson commented on CASSANDRA-5220:
------------------------------------------

Sorry about the unit tests, I had some problems with ant and junit when I 
uploaded the patch so I ran those tests through eclipse and it seems that I 
missed the -ea flag. Also the tests in SerializationsTest seems to be 
broken(due to the changes for validations). The other two failing tests seems 
to be failing on trunk as well, so I'm assuming that it's not due to this patch.

I'm working based on your rebased branch 5220 and have fixed the unit tests 
[here|https://github.com/emolsson/cassandra/commits/5220].

Also I seem to be having some problems with running the dtests, is it something 
special that needs to be done to run the dtests on trunk? I get the following 
error message:
{noformat}
NoHostAvailable: ('Unable to connect to any servers', {'127.0.0.1': 
InvalidRequest(u'code=2200 [Invalid query] message="unconfigured table 
schema_keyspaces"',)})
{noformat}


> 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)

Reply via email to