[
https://issues.apache.org/jira/browse/CASSANDRA-435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12776452#action_12776452
]
Jonathan Ellis commented on CASSANDRA-435:
------------------------------------------
1) LEAVING/NORMAL don't get re-broadcast though, so they remain part of the app
state but they won't ever be seen again by onChange. So as long as LEFT isn't
part of the same gossip as leaving (and the sleep ensures it won't) in practice
LEFT is already the last thing gossipped (and we shut down the gossiper right
afterwards). This works as planned in my testing. I'm fine with patches
improving this but it's not strictly necessary.
2) No, the pending ranges aren't to say "i'm busy streaming" but "when the
planned ring changes finish, this will be my range, so I need writes for that
range in the meantime so I'm not out of date when the change-over happens." So
the right place to remove those is in the STATE_LEFT change. I will add it
there.
I will look at the 04 patch shortly.
> 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.
