cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CASSANDRA-435) unbootstrap
Date Fri, 06 Nov 2009 22:40:32 GMT

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

Jonathan Ellis commented on CASSANDRA-435:
------------------------------------------

With 525 done I think the rest looks like this

 * unbootstrapping node gossips STATE_LEAVING: token
 * other nodes use that to set pending ranges on the nodes that will be responsible for the
replica ranges it has, similar to UpdateBoostrapRanges (but you can't just call strategy.getPendingRanges
since we're adding ranges to existing nodes rather than a new one -- can we just use strategy.getAddressRanges
and figure out which node will get each Range?)
 * stream over the data
 * gossip STATE_LEFT. other nodes remove it from the gossip network (this automatically makes
new node ranges look like what they would have been w/ pendingranges merged).  probably worth
looking at old MemberShipcleaner code that was r/m'd in r828130.

> unbootstrap
> -----------
>
>                 Key: CASSANDRA-435
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-435
>             Project: Cassandra
>          Issue Type: New Feature
>            Reporter: Jonathan Ellis
>            Assignee: Jonathan Ellis
>             Fix For: 0.5
>
>
> add JMX command to tell a node to decommission itself (moving its data to the next node
on the ring)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message