You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Stefan Miklosovic (Jira)" <ji...@apache.org> on 2022/11/21 08:03:00 UTC

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

    [ https://issues.apache.org/jira/browse/CASSANDRA-18025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17636513#comment-17636513 ] 

Stefan Miklosovic commented on CASSANDRA-18025:
-----------------------------------------------

[~brandon.williams] what do you think about this? It is ok that it fixes the connection when one node is down, on the other hand, should not be a user notified about that node being down before a stress test starts? In that sense, it is good that it fails. I would not want to start my stress test on a three node cluster when one of the nodes is down and I do not know it.

[~fruch] could you please expand your thinking around "management operation / expanding / shrinking"? Is it common for you to perform a stress test on a cluster which changes its topology? Why would expanding of a cluster make the driver not being able to connect to a node which was there already?

> 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
>            Priority: Normal
>             Fix For: 3.0.x, 3.11.x, 4.0.x, 4.1.x, 4.2
>
>          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: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org