[
https://issues.apache.org/jira/browse/CASSANDRA-435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12776495#action_12776495
]
Jonathan Ellis commented on CASSANDRA-435:
------------------------------------------
1) simplest thing is to leave the node in gossip, but remove it from
tokenmetadata. this means gossip can tell nodes that were down temporarily
about the new state, as designed, w/o nasty hacks. if/when someone actually
needs to add/remove so many nodes that clutter of internal Gossiper state
becomes a problem, he can patch it. :)
2) added ARS.removeObsoletePendingRanges that idempotently removes pending
ranges that are no longer needed because the ring has updated to reflect the
pending state change. this approach reduces the chance of accidentally
removing something we shouldn't.
3) applied 04 patch
> 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
>
> Attachments:
> 0001-CASSANDRA-435-clean-up-transfer-code-from-BMVH-move-t.txt,
> 0002-move-more-generic-streaming-code-into-Streaming.java.txt,
> 0003-add-leaving-mode.txt, 0004-simplify-getChangedRangesForLeaving.txt,
> 435-modify-update_leaving_ranges.txt
>
>
> 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.
