[
https://issues.apache.org/jira/browse/CASSANDRA-18025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17724165#comment-17724165
]
Stefan Miklosovic edited comment on CASSANDRA-18025 at 5/19/23 7:30 AM:
------------------------------------------------------------------------
3.0
https://app.circleci.com/pipelines/github/instaclustr/cassandra/2239/workflows/2358d608-7756-4b94-ba84-bd3eb5104e57
3.11
https://app.circleci.com/pipelines/github/instaclustr/cassandra/2238/workflows/8ab419e4-96e0-42a8-8be3-cbba634a2d48
4.0 j8
https://app.circleci.com/pipelines/github/instaclustr/cassandra/2237/workflows/b22a3b8c-4de3-4d48-a3f0-9d44a7dd316d
4.0 j11
https://app.circleci.com/pipelines/github/instaclustr/cassandra/2237/workflows/9c090b86-9493-4536-8e4b-a3a58dca716a
4.1 j11
https://app.circleci.com/pipelines/github/instaclustr/cassandra/2236/workflows/9f17a644-d5f6-4018-b169-e1e99b363d47
4.1 j8
https://app.circleci.com/pipelines/github/instaclustr/cassandra/2236/workflows/431febd5-d0f4-42e7-b694-49245f53ce04
trunk TBD
[~brandon.williams] I would appreciated if you run trunk for me - this branch
https://app.circleci.com/pipelines/github/instaclustr/cassandra?branch=CASSANDRA-18025
4.1 is still running as I write this. I believe that if all is nice I would be
able to merge this today evening UTC if you help with trunk. Thanks.
I also manually tested this on trunk and it behaves nicely. If I run a stress
against 3 nodes and turn off one of them, it just continues fine which can not
be told about the current solution.
There is also -nodes file=path flag to specify nodes in a file, one per line. A
user would expect that all three nodes are used but that is not true, just
random one, which is misleading (without this patch merged).
was (Author: smiklosovic):
3.0
https://app.circleci.com/pipelines/github/instaclustr/cassandra/2239/workflows/2358d608-7756-4b94-ba84-bd3eb5104e57
3.11
https://app.circleci.com/pipelines/github/instaclustr/cassandra/2238/workflows/8ab419e4-96e0-42a8-8be3-cbba634a2d48
4.0 j8
https://app.circleci.com/pipelines/github/instaclustr/cassandra/2237/workflows/b22a3b8c-4de3-4d48-a3f0-9d44a7dd316d
4.0 j11
https://app.circleci.com/pipelines/github/instaclustr/cassandra/2237/workflows/9c090b86-9493-4536-8e4b-a3a58dca716a
4.1 j11
https://app.circleci.com/pipelines/github/instaclustr/cassandra/2236/workflows/9f17a644-d5f6-4018-b169-e1e99b363d47
4.1 j8
https://app.circleci.com/pipelines/github/instaclustr/cassandra/2236/workflows/431febd5-d0f4-42e7-b694-49245f53ce04
trunk TBD
[~brandon.williams] I would appreciated if you run trunk for me - this branch
https://app.circleci.com/pipelines/github/instaclustr/cassandra?branch=CASSANDRA-18025
4.1 is still running as I write this. I believe that if all is nice I would be
able to merge this today evening UTC if you help with trunk. Thanks.
> 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.x, 3.11.x, 4.0.x, 4.1.x, 5.0
>
> 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]
