cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sam Overton (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-4122) Bootstrap and decommission with multiple ranges for vnodes
Date Wed, 11 Jul 2012 16:21:34 GMT


Sam Overton commented on CASSANDRA-4122:

Added num_tokens note to NEWS.txt:
> Bootstrap and decommission with multiple ranges for vnodes
> ----------------------------------------------------------
>                 Key: CASSANDRA-4122
>                 URL:
>             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
> _Edit0: appended patch information._
> _Edit1: added 03_group_stream_out_ranges patch._
> h3. Patches
> ||Compare||Raw diff||Description||
> |[01_bootstrap_decommission|]|[01_bootstrap_decommission.patch|]|No
> |[02_remove_tokens|]|[02_remove_tokens.patch|]|No
> |[03_group_stream_out_ranges|]|[03_group_stream_out_ranges.patch|]|No
> ----
> _Note: These are branches managed with TopGit. If you are applying the patch output manually,
you will either need to filter the TopGit metadata files (i.e. {{wget -O - <url> | filterdiff
-x*.topdeps -x*.topmsg | patch -p1}}), or remove them afterward ({{rm .topmsg .topdeps}})._

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message