[
https://issues.apache.org/jira/browse/CASSANDRA-15120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16839636#comment-16839636
]
Sam Tunnicliffe commented on CASSANDRA-15120:
---------------------------------------------
I share your concerns around making changes to this area in 3.0, but I've spent
some time working through this and I believe that this change is correct. I
haven't really looked at any of non-test changes made to support
gossip/networking in the tests yet, but I'll make another pass at it when
you're done with those.
> Nodes that join the ring while another node is MOVING build an invalid view
> of the token ring
> ---------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-15120
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15120
> Project: Cassandra
> Issue Type: Bug
> Components: Cluster/Gossip, Cluster/Membership
> Reporter: Benedict
> Assignee: Benedict
> Priority: Normal
>
> Gossip only updates the token metadata for nodes in the NORMAL, SHUTDOWN or
> LEAVING* statuses. MOVING and REMOVING_TOKEN nodes do not have their ring
> information updated (nor do others, but these other states _should_ only be
> taken by nodes that are not members of the ring).
> If a node missed the most recent token-modifying events because they were not
> a member of the ring when they happened (or because Gossip was delayed to
> them), they will retain an invalid view of the ring until the node enters the
> one of the NORMAL, SHUTDOWN or LEAVING states.
> *LEAVING is populated differently, however, and in a probably unsafe manner
> that this work will also address.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
