[
https://issues.apache.org/jira/browse/CASSANDRA-541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12777513#action_12777513
]
Jaakko Laine commented on CASSANDRA-541:
----------------------------------------
Yeah, we can move from LEAVING to BOOTSTRAPPING, but then we'll need to remove
the endpoint from tokenmetadata and remove obsolete pending ranges whenever a
node bootstraps. This is exactly what LEFT does, so seems like a nice way to go
through that state, but we can of course do that in bootstrapping. The only
problem then is that if we always clear tokenmetadata and pending ranges in
bootstrap, we cannot distinguish between a legitimate move-bootsrap and a node
that enters the cluster using an old IP address and a new token. It is a matter
of taste what should be the proper action in this case, but if we clear
tokenmetadata, we won't be able to even report an error on this.
> allow moving a live node with data on it
> ----------------------------------------
>
> Key: CASSANDRA-541
> URL: https://issues.apache.org/jira/browse/CASSANDRA-541
> Project: Cassandra
> Issue Type: New Feature
> Components: Core, Tools
> Reporter: Jonathan Ellis
> Assignee: Jonathan Ellis
> Fix For: 0.5
>
> Attachments: 0001-CASSANDRA-541-add-Move-command.txt,
> 0002-miscellaneous-fixes.txt,
> 0003-fix-for-when-bootstrap-source-has-no-data-in-the-range.txt,
> 0004-workaround-for-Resource-temporarily-unavailable.txt,
> 0005-fix-pending-ranges-handling-in-node-move.txt
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
