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 Tue, 08 Feb 2011 16:59:57 GMT


Nick Bailey commented on CASSANDRA-1427:

bq. 2. In StorageService.handleStateMoving store both new token and InetAddress of the moving

Not sure what you mean.

bq. 3. Add following code to calculatePendingRanges(AbstractReplicationStrategy, String) after
bootstrapToken ranges calculation to track pending ranges of the moving nodes (almost the
same code as for bootstrapping nodes):

I think this is the right approach. Would it be useful to get rid of 'movingRanges' in TMD
and simply add nodes that are moving to both the leaving endpoints and the bootstrap tokens.
I think this would remove the need to change calculate pending ranges at all. I could see
how the distinction between moving and leaving+bootstrap might be easier to follow in the
code though.

> 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