[CASSANDRA-15912] Occasional NEW_NODE event sent instead of NODE_UP in dTest

• Type: Bug
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 4.0-beta1, 4.0
• Component/s: Messaging/Client
• Bug Category: Correctness - Test Failure
• Severity: Normal
• Complexity: Normal
• Discovered By: Unit Test
• Platform: All
• Since Version: 4.0-alpha4

Source Control Link

https://github.com/apache/cassandra-dtest/commit/30806d425e2271b982bf8facb174341b6b4193ed

Test and Documentation Plan

See PR

• Assignee: Berenguer Blasi
• Reporter: Bryn Cooke

Authors

Berenguer Blasi

Reviewers

Brandon Williams

• Created: 02/Jul/20 10:23
• Updated: 21/Dec/20 09:32
• Resolved: 08/Jul/20 16:18

Description

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.

 

Issue Links

• relates to: CASSANDRA-15677 Topology events are not sent to clients if the nodes use the same network interface
• relates to: CASSANDRA-11038 Is node being restarted treated as node joining?
• links to: CASSANDRA-15912 dtests PR