[CASSANDRA-18780] ConnectionBurnTest fails with NullPointerException

• Type: Bug
• Status: Patch Available
• Priority: Normal
• Resolution: Unresolved
• Fix Version/s: 5.x
• Component/s: Test/burn
• Bug Category: Correctness
• Severity: Normal
• Complexity: Challenging
• Discovered By: User Report
• Platform: All

Test and Documentation Plan

Run ConnectionBurnTest locally.

• Assignee: Maxim Muzafarov
• Reporter: Maxim Muzafarov

Authors

Maxim Muzafarov

• Created: 19/Aug/23 17:26
• Updated: 11/Oct/23 15:05

Description

The ConnectionBurnTest is used to check the throughput of outgoing and incoming connections and report the results of execution to the log. During the test run, I noticed a couple of errors that actually prevent us from getting any results.

1. The NullPointerException is thrown during the test execution

   java.lang.NullPointerException: null
   	at org.apache.cassandra.metrics.ClientMetrics.unpauseConnection(ClientMetrics.java:69)
   	at org.apache.cassandra.net.AbstractMessageHandler.onReserveCapacityRegained(AbstractMessageHandler.java:314)
   	at org.apache.cassandra.net.AbstractMessageHandler.onGlobalReserveCapacityRegained(AbstractMessageHandler.java:289)
   	at org.apache.cassandra.net.AbstractMessageHandler$WaitQueue$Ticket.reactivateHandler(AbstractMessageHandler.java:792)
   	at org.apache.cassandra.net.AbstractMessageHandler$WaitQueue$ReactivateHandlers.run(AbstractMessageHandler.java:740)
   

2. The exception is swallowed and the test exits almost immediately, but the exception itself is not rethrown and the exit code is zero. The test is always green on CI, but a fatal exception has occurred;

Issue Links

• relates to: CASSANDRA-16360 CRC32 is inefficient on x86
• links to: GitHub PullRequest: 2613