cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eric Evans (JIRA)" <>
Subject [jira] [Updated] (CASSANDRA-4127) migration support for vnodes
Date Wed, 18 Jul 2012 19:19:35 GMT


Eric Evans updated CASSANDRA-4127:

    Fix Version/s: 1.2
> migration support for vnodes
> ----------------------------
>                 Key: CASSANDRA-4127
>                 URL:
>             Project: Cassandra
>          Issue Type: Sub-task
>          Components: Core
>            Reporter: Sam Overton
>            Assignee: Sam Overton
>              Labels: vnodes
>             Fix For: 1.2
> If, when starting up for the first time, the host only has 1 token but num_tokens is
configured differently, then this will trigger a migration process:
> * The host will assign itself num_tokens tokens in its own range
> * The new tokens will be gossiped
> This will allow a rolling migration where N new hosts are bootstrapped into the cluster
(with num_tokens set appropriately) and then the N old nodes are decommissioned. This will
result in even distribution of the data among the new nodes with randomly assigned tokens.
> _Edit0: Appended patch information._
> h3. Patches
> ||Compare||Raw diff||Description||
> |[01_migration_path|]|[01_migration_path.patch|]|Migrate
from one token to many|
> ----
> _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