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

Jaakko Laine commented on CASSANDRA-435:
----------------------------------------

I think there are two problems with this patchset:

(1) After the leaving node gossips STATE_LEFT, its gossiper continues to 
broadcast application state, which still includes NORMAL (and LEAVING) from 
previous states. When other nodes get STATE_LEFT, they remove all information 
about this node, which will cause them to interpret the following gossip 
message as new join. Don't know if stopping the gossiper from broadcasting 
anything more after STATE_LEFT, would cause other nodes to convict it. This 
would be the simplest solution, but probably need to do something more creative 
to better handle all possible state transitions.

(2) When all data for a pending range has been streamed, the receiving node 
should inform about the completion, otherwise pending ranges won't be removed. 
The simplest way would be to just gossip its token again, as this will cause 
pending ranges for this endpoint to be removed. Problem is the receiving end 
does not know when whole data transfer is complete as tables are streamed one 
by one. Another possibility would be for the leaving node to gossip these 
endpoints as a part of its STATE_LEFT message.


> 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.

Reply via email to