cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Brown (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-5337) vnode-aware replacenode command
Date Mon, 15 Jul 2013 20:50:48 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-5337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13708959#comment-13708959
] 

Jason Brown commented on CASSANDRA-5337:
----------------------------------------

v2 lgtm.
                
> 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: 1.2.7, 2.0
>
>         Attachments: 5337.txt, 5337-v2.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

Mime
View raw message