[CASSANDRA-18025] cassandra-stress: not all contact point are passed down to driver

• Type: Bug
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 3.0.30, 3.11.16, 4.0.10, 4.1.2, 5.0-alpha1, 5.0
• Component/s: Tool/stress
• Bug Category: Correctness - Transient Incorrect Response
• Severity: Normal
• Complexity: Low Hanging Fruit
• Discovered By: User Report
• Platform: All
• Since Version: 3.0.0

Source Control Link

https://github.com/apache/cassandra/commit/b828f7ea1b735586da388ddfee17f26685e20cef

Test and Documentation Plan

CI

• Assignee: Stefan Miklosovic
• Reporter: Israel Fruchter

Authors

Stefan Miklosovic

Reviewers

Brandon Williams

• Created: 08/Nov/22 15:23
• Updated: 12/Sep/23 13:03
• Resolved: 19/May/23 18:22

Description

Seem like c-s is randomly selecting a node from the nodes passed down to it in the command line, and use that node as contact point to the driver.

 

When using c-s together with other management operations (for example expending/shrinking the cluster), we can get into situation some of the nodes mentioned in the command line aren't reachable/available, and c-s instead of applying the best practice of having multiple contact points, pass down only one that can be unavailable and fail completely without trying any of the other nodes mentioned in the command line

we just fixed that in our fork of cassandra-stress:

https://github.com/scylladb/scylla-tools-java/pull/314

 

Issue Links

• links to: GitHub Pull Request #1989
• links to: GitHub Pull Request #2343
• links to: GitHub Pull Request #2344
• links to: GitHub Pull Request #2345
• links to: GitHub Pull Request #2346
• links to: GitHub Pull Request #2347