[jira] [Commented] (CASSANDRA-4127) migration support for vnodes
[
https://issues.apache.org/jira/browse/CASSANDRA-4127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13417285#comment-13417285
]
Brandon Williams commented on CASSANDRA-4127:
-
bq. Since we already have vnode migration for bootstrap / decommission,
couldn't we just add a nodetool shuffle command to do that in-place instead?
Created CASSANDRA-4443 for this.
+1
migration support for vnodes
Key: CASSANDRA-4127
URL: https://issues.apache.org/jira/browse/CASSANDRA-4127
Project: Cassandra
Issue Type: Sub-task
Components: Core
Reporter: Sam Overton
Assignee: Sam Overton
Labels: vnodes
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|https://github.com/acunu/cassandra/compare/top-bases/p/4127/01_migration_path...p/4127/01_migration_path]|[01_migration_path.patch|https://github.com/acunu/cassandra/compare/top-bases/p/4127/01_migration_path...p/4127/01_migration_path.diff]|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:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CASSANDRA-4127) migration support for vnodes
[
https://issues.apache.org/jira/browse/CASSANDRA-4127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13411809#comment-13411809
]
Jonathan Ellis commented on CASSANDRA-4127:
---
bq. 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.
That's a fairly painful / expensive proposition.
Since we already have vnode migration for bootstrap / decommission, couldn't we
just add a {{nodetool shuffle}} command to do that in-place instead?
migration support for vnodes
Key: CASSANDRA-4127
URL: https://issues.apache.org/jira/browse/CASSANDRA-4127
Project: Cassandra
Issue Type: Sub-task
Components: Core
Reporter: Sam Overton
Assignee: Sam Overton
Labels: vnodes
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|https://github.com/acunu/cassandra/compare/top-bases/p/4127/01_migration_path...p/4127/01_migration_path]|[01_migration_path.patch|https://github.com/acunu/cassandra/compare/top-bases/p/4127/01_migration_path...p/4127/01_migration_path.diff]|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:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
