[
https://issues.apache.org/jira/browse/CASSANDRA-18025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Miklosovic updated CASSANDRA-18025:
------------------------------------------
Fix Version/s: 3.0.29
4.0.10
4.1.2
3.11.16
(was: 3.0.x)
(was: 3.11.x)
(was: 4.0.x)
(was: 4.1.x)
Since Version: 3.0.0
Source Control Link:
https://github.com/apache/cassandra/commit/b828f7ea1b735586da388ddfee17f26685e20cef
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
> cassandra-stress: not all contact point are passed down to driver
> -----------------------------------------------------------------
>
> Key: CASSANDRA-18025
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18025
> Project: Cassandra
> Issue Type: Bug
> Components: Tool/stress
> Reporter: Israel Fruchter
> Assignee: Stefan Miklosovic
> Priority: Normal
> Fix For: 3.0.29, 4.0.10, 4.1.2, 5.0, 3.11.16
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> 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]
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
