[jira] [Updated] (CASSANDRA-4127) migration support for vnodes
[ https://issues.apache.org/jira/browse/CASSANDRA-4127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Evans updated CASSANDRA-4127: -- Fix Version/s: 1.2 > 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 > 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|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 - | 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] [Updated] (CASSANDRA-4127) migration support for vnodes
[ https://issues.apache.org/jira/browse/CASSANDRA-4127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Ellis updated CASSANDRA-4127: -- Reviewer: brandon.williams > 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 - | 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] [Updated] (CASSANDRA-4127) migration support for vnodes
[ https://issues.apache.org/jira/browse/CASSANDRA-4127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Evans updated CASSANDRA-4127: -- Description: 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 - | filterdiff -x*.topdeps -x*.topmsg | patch -p1}}), or remove them afterward ({{rm .topmsg .topdeps}})._ was: 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. Labels: vnodes (was: ) > 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 - | 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