[
https://issues.apache.org/jira/browse/CASSANDRA-15120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16854730#comment-16854730
]
Sam Tunnicliffe commented on CASSANDRA-15120:
---------------------------------------------
bq. The trunk version does not include the dtest, as much of the plumbing to
support that is going to land in CASSANDRA-15066.
CASSANDRA-15148
bq. The change to 3.0 also breaks backward compatibility of the cross version
dtests with 2.2.
CASSANDRA-15147
bq. In the unit tests, RowFilterTest, which was recently added for
CASSANDRA-15126, appears to be failing on 3.11 only.
Ninja'd a fix in
[7f4ecb0|https://github.com/apache/cassandra/commit/7f4ecb01247088e27ff2ae15aa5375805bada53a]
> 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
> Fix For: 3.0.19, 3.11.5, 4.0
>
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
