[
https://issues.apache.org/jira/browse/CASSANDRA-5337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brandon Williams updated CASSANDRA-5337:
----------------------------------------
Attachment: 5337.txt
Patch basically follows replace_token, but instead takes a host id and looks up
the tokens.
> vnode-aware replacenode command
> -------------------------------
>
> Key: CASSANDRA-5337
> URL: https://issues.apache.org/jira/browse/CASSANDRA-5337
> Project: Cassandra
> Issue Type: New Feature
> Components: Core
> Affects Versions: 1.2.0
> Reporter: Jonathan Ellis
> Assignee: Brandon Williams
> Labels: vnodes
> Fix For: 2.0
>
> Attachments: 5337.txt
>
>
> Currently you have the following options to replace a dead, unrecoverable
> node:
> - replacetoken. this requires specifying all 256 or so vnode tokens as a CSL
> - bootstrap new node, decommission old one. this is inefficient since the
> new node's vnodes will probably not overlap much with the old one's, so we
> replicate stream about 2x as much as if we were just replacing the old with
> the new
> We should add an analogue to replacetoken that takes the address or node ID
> of the dead node instead.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
