[
https://issues.apache.org/jira/browse/CASSANDRA-15912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17153558#comment-17153558
]
Berenguer Blasi commented on CASSANDRA-15912:
---------------------------------------------
The original problem was that the node2 restart could happen before the
original NEW_NODE had been sent, so upon node2 becoming UP again it would get
that NEW_NODE on top. Waiting to restart once all notifications have gone
through fixes the issue.
No CI runs as it would be an overkill. It failed and now passes locally:
repro'ed against 3.0, 3.11 and 4.0.
> Occasional NEW_NODE event sent instead of NODE_UP in dTest
> ----------------------------------------------------------
>
> Key: CASSANDRA-15912
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15912
> Project: Cassandra
> Issue Type: Bug
> Components: Messaging/Client
> Reporter: Bryn Cooke
> Assignee: Berenguer Blasi
> Priority: Normal
> Fix For: 4.0-beta
>
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> A new test for topology events in CASSANDRA-15677 is occasionally failing due
> to a NEW_NODE event sent instead of NODE_UP.
> For instance:
> [https://app.circleci.com/pipelines/github/jasonstack/cassandra/231/workflows/cdf55335-c876-450b-8bf9-1d778a2df806/jobs/2240]
>
> Previously topology events were not been sent at all, so it is possible that
> this is a long standing bug.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
