Skip to content

Conversation

@fruch
Copy link

@fruch fruch commented Nov 8, 2022

cassandra-stress: not all contact point are passed down to driver

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 practices 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.

patch by Israel Fruchter(@fruch) for CASSANDRA-18025

@fruch fruch changed the title CASSANDRA-18025: cassandra-stress: not all contact point are passed d… CASSANDRA-18025: cassandra-stress: not all contact point are passed down to driver Nov 8, 2022
…own to driver

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 practices
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.

patch by Israel Fruchter(@fruch) for CASSANDRA-18025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants