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 Wed, 25 Aug 2010 18:07:17 GMT


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

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:
>             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
> We should add functionality to optimize moves that take/give ranges to a node's direct

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message