-
Notifications
You must be signed in to change notification settings - Fork 623
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
too many (100k) concurrent queries produce errors #1731
Comments
It seems that this issue is not a bug, since java driver behaves pretty much the same:
1_000 workers are handled gracefully, while 2_000 give errors like
|
However with java driver adding the following config to CqlSession
allows to sustain heavy load from client code. So this issue may be not a bug, but a feature request for similar throttler in gocql. |
I would like to handle this issue, working on it |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Please answer these questions before submitting your issue. Thanks!
What version of Cassandra are you using?
4.1.3 or 5.0
What version of Gocql are you using?
1.6.0
What version of Go are you using?
1.21.1
What did you do?
docker run --rm --name=cassandra -p 9042:9042 cassandra:4.1.3
What did you expect to see?
I expect the program to finish successfully.
What did you see instead?
I see errors
or
Note: changing
workers
const to 50_000 allows the program to finish gracefully (increasingqueries
const is possible also - program will work minutes instead of seconds but still will finish gracefully with 50_000 workers)The text was updated successfully, but these errors were encountered: