[jira] Commented: (CASSANDRA-1427) Optimize loadbalance/move for moves within the current range

["Nick Bailey (JIRA)" <ji...@apache.org>]

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

Nick Bailey commented on CASSANDRA-1427:
----------------------------------------

Currently a move is just decommission then bootstrap.  This means that if loadbalance is called, the token the node is going to move to isn't calculated until the node has fully left the ring.

It might make sense for this ticket to implement this as a special case for when a token to move to is actually specified.  Any loadbalancer implemented in CASSANDRA-1418 will need to calculate the token it plans to move to before the move operation takes place.  

> 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: Nick Bailey
>             Fix For: 0.8
>
>
> 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.
-
You can reply to this email to add a comment to the issue online.