cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sam Overton (Updated) (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-4122) Bootstrap and decommission with multiple ranges for vnodes
Date Thu, 05 Apr 2012 14:42:26 GMT

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

Sam Overton updated CASSANDRA-4122:
-----------------------------------

    Description: 
Bootstrap:
* New config parameter num_tokens which is used iff initial_token is not set. 
* Both initial_token and replace_token will allow a comma-separated list of tokens so multiple
tokens can be configured explicitly if required.
* Bootstrapper.getBalancedToken will be deprecated and used only in the case that num_tokens
== 1. Instead, if initial token is not specified, num_tokens tokens will be randomly chosen.
* The existing logic can be used to calculate the new ranges which must be streamed.

Decommission:
* The existing logic can be used with some minor modifications to account for multiple tokens
per host

    
> Bootstrap and decommission with multiple ranges for vnodes
> ----------------------------------------------------------
>
>                 Key: CASSANDRA-4122
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-4122
>             Project: Cassandra
>          Issue Type: Sub-task
>          Components: Core
>            Reporter: Sam Overton
>            Assignee: Sam Overton
>
> Bootstrap:
> * New config parameter num_tokens which is used iff initial_token is not set. 
> * Both initial_token and replace_token will allow a comma-separated list of tokens so
multiple tokens can be configured explicitly if required.
> * Bootstrapper.getBalancedToken will be deprecated and used only in the case that num_tokens
== 1. Instead, if initial token is not specified, num_tokens tokens will be randomly chosen.
> * The existing logic can be used to calculate the new ranges which must be streamed.
> Decommission:
> * The existing logic can be used with some minor modifications to account for multiple
tokens per host

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message