[
https://issues.apache.org/jira/browse/CASSANDRA-4559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13439841#comment-13439841
]
Brandon Williams commented on CASSANDRA-4559:
---------------------------------------------
bq. It doesn't make a huge difference to me either way; I can make the
operation support multiple ranges in a call if you prefer.
It seems like that would be handy, though now you need to be able to
communicate multiple tokens in the status... which almost brings us back around
to the status-appending game we want to avoid in CASSANDRA-4383 :(
bq. Don't we need to continue supporting the old-style move for users that want
to continue running with 1 token per node?
You're right, there's a difference between "I'm moving to that token" (move)
and "I'm taking this token from this other node" (relocate)
> implement token relocation
> --------------------------
>
> Key: CASSANDRA-4559
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4559
> Project: Cassandra
> Issue Type: Sub-task
> Components: Core, Tools
> Reporter: Eric Evans
> Assignee: Eric Evans
> Labels: vnodes
>
> Whatever the specifics of a _shuffle_ (see CASSANDRA-4443), it will be
> necessary to relocate a range from one node to another.
> _Edit0: Linked in new patch containing tests._
> ----
> h3. Patches
> ||Compare||Raw diff||Description||
> |[010_refactor_range_move|https://github.com/acunu/cassandra/compare/top-bases/p/4443/010_refactor_range_move...p/4443/010_refactor_range_move]|[010_refactor_range_move.patch|https://github.com/acunu/cassandra/compare/top-bases/p/4443/010_refactor_range_move...p/4443/010_refactor_range_move.diff]|No
> Description|
> |[020_calculate_pending|https://github.com/acunu/cassandra/compare/top-bases/p/4443/020_calculate_pending...p/4443/020_calculate_pending]|[020_calculate_pending.patch|https://github.com/acunu/cassandra/compare/top-bases/p/4443/020_calculate_pending...p/4443/020_calculate_pending.diff]|No
> Description|
> |[030_relocate_token|https://github.com/acunu/cassandra/compare/top-bases/p/4443/030_relocate_token...p/4443/030_relocate_token]|[030_relocate_token.patch|https://github.com/acunu/cassandra/compare/top-bases/p/4443/030_relocate_token...p/4443/030_relocate_token.diff]|No
> Description|
> |[040_tests|https://github.com/acunu/cassandra/compare/top-bases/p/4443/040_tests...p/4443/040_tests]|[040_tests.patch|https://github.com/acunu/cassandra/compare/top-bases/p/4443/040_tests...p/4443/040_tests.diff]|No
> Description|
> ----
> _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
