[CASSANDRA-16511] Running tests in parallel can sometimes result in port collision

• Type: Bug
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 4.0-rc1, 4.0
• Component/s: Test/unit
• Bug Category: Code
• Severity: Low
• Complexity: Low Hanging Fruit
• Discovered By: User Report
• Platform: All
• Since Version: 4.0-alpha1

Source Control Link

https://github.com/apache/cassandra/commit/11d069a766a4a9a5db534a86de0175128431526f https://github.com/apache/cassandra-builds/commit/34d9592dda05ab313efac9d04e565f593fa40b37 https://github.com/apache/cassandra/commit/1f7700cf8bd6364f49138472b47676e46c0

Test and Documentation Plan

Try to reproduce using the provided steps

• Assignee: Jacek Lewandowski
• Reporter: Jacek Lewandowski

Authors

Jacek Lewandowski

Reviewers

Brandon Williams, Michael Semb Wever

• Created: 11/Mar/21 14:20
• Updated: 19/Nov/21 06:49
• Resolved: 12/Mar/21 20:42

Description

When running unit tests with parallel execution we may sometimes notice the port collision. In this mode, test classes from the list get consecutive offsets which are added to native transport port, storage port and ssl storage port ( OffsetAwareConfigurationLoader ). However we add to the ports configured in test/conf/cassandra.yaml we as we can see we have the following default config:

storage_port: 7012
ssl_storage_port: 7011 

This results in the situation that thread n has the same storage port as thread n+1 has ssl storage port. There are not much such tests, but we can see ConnectionTests failing frequently because of that. 

The other problem is that OffsetAwareConfigurationLoader does not adjust native transport ssl port.

 

Patch at https://github.com/apache/cassandra/pull/925