[jira] [Updated] (CASSANDRA-5337) vnode-aware replacenode command

["Ryan McGuire (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CASSANDRA-5337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ryan McGuire updated CASSANDRA-5337:
------------------------------------

    Labels: qa-resolved  (was: vnodes)

> 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: qa-resolved
>             Fix For: 1.2.7, 2.0.0
>
>         Attachments: 5337-v2.txt, 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 was sent by Atlassian JIRA
(v6.2#6252)