[jira] Updated: (CASSANDRA-574) loadbalance should first leave and then determine new token

["Jaakko Laine (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CASSANDRA-574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jaakko Laine updated CASSANDRA-574:
-----------------------------------

    Attachment: 574.patch

Modify move function to get balanced token at bootstrap time if token given as a parameter was null.

> loadbalance should first leave and then determine new token
> -----------------------------------------------------------
>
>                 Key: CASSANDRA-574
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-574
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: 0.5
>            Reporter: Jaakko Laine
>            Priority: Minor
>             Fix For: 0.5
>
>         Attachments: 574.patch
>
>
> It would be better for loadbalance command to first leave old token and only at re-bootstrap time determine balanced token. This way we not only get to determine it according to the latest load info, but also reduce the slightly fragile timeframe between deciding a token to boot to, and actually booting to it.

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