cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nick Bailey (JIRA)" <>
Subject [jira] Commented: (CASSANDRA-1427) Optimize loadbalance/move for moves within the current range
Date Sat, 05 Feb 2011 21:47:30 GMT


Nick Bailey commented on CASSANDRA-1427:

* Seems like move should just fail if token is null.
* Shouldn't the pending ranges calculation include the tokens the nodes are moving too as
** It also looks like the writeEndpoints calculation in token metadata is just a list rather
than a set. So we could potentially be adding the same endpoint multiple times here. Best
solution is probably to make that calculation return a set.
* A already exists. The fact that its still passing is probably indicative of
it's usefulness but it should probably be updated and hopefully made more useful.

> Optimize loadbalance/move for moves within the current range
> ------------------------------------------------------------
>                 Key: CASSANDRA-1427
>                 URL:
>             Project: Cassandra
>          Issue Type: Sub-task
>          Components: Core
>    Affects Versions: 0.7 beta 1
>            Reporter: Nick Bailey
>            Assignee: Pavel Yaskevich
>             Fix For: 0.8
>         Attachments: CASSANDRA-1427-v2.patch, CASSANDRA-1427.patch
>   Original Estimate: 42h
>          Time Spent: 42h
>  Remaining Estimate: 0h
> Currently our move/loadbalance operations only implement case 2 of the Ruhl algorithm
described at
> We should add functionality to optimize moves that take/give ranges to a node's direct

This message is automatically generated by JIRA.
For more information on JIRA, see:


View raw message