[
https://issues.apache.org/jira/browse/CASSANDRA-1427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12991068#comment-12991068
]
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 well?
** 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 MoveTest.java 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: https://issues.apache.org/jira/browse/CASSANDRA-1427
> 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
> https://issues.apache.org/jira/browse/CASSANDRA-192#action_12713079.
> We should add functionality to optimize moves that take/give ranges to a
> node's direct neighbors.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
