-
Notifications
You must be signed in to change notification settings - Fork 59
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
Integration tests fail using Scylla 5.2.x #126
Comments
|
Only Scylla docker image version was changed. |
running the same with master, and in 300s it got killed by my kernel:
|
@avelanarius / @zimnx can someone please take a look at this? |
I will look into it. |
This test failure due to the unabling execute prepared statement due to the getting Same problem from |
that issue in java-driver wasn't fixed, and was fixed on scylla end in some way. |
I have run this test locally on |
I ran it via integration.sh and it did fail, will look at the difference tomorrow |
Most likely it is driver issue, it's logic does not cover the case when prepared statement cache on If this is true, then all our and upstream drivers have exact same issue, which is not regression and only regression there is that I have opened issue on the |
That particular one was fixed by: scylladb/scylladb#10456 (seehttps://github.com/scylladb/scylladb/issues/10440) |
From scylladb/scylladb#14338 :
Which confirms my assumption, it is needed to be fixed on |
PR to increase memory limit - #128 to avoid hitting the issue |
fix(docker-compose.yaml): increase memory limit to avoid hitting #126
Thanks, closing. |
Please answer these questions before submitting your issue. Thanks!
What version of Scylla or Cassandra are you using?
5.2.1 and 5.2.0
What version of Gocql are you using?
v1.7.3
What version of Go are you using?
1.20.4
What did you do?
I explicitly defined the Scylla version:
Then ran tests:
And got following result:
What did you expect to see?
I expect it to work ok like with all other more older Scylla versions
5.1.x
,5.0.x
and4.6.x
which provide following result:What did you see instead?
I see constant connection
300s
timeouts.If you are having connectivity related issues please share the following additional information
Describe your Cassandra cluster
please provide the following information
nodetool status
:CQLSH
:With
gocql_debug
:gocql_debug_for_issue_126.log
The text was updated successfully, but these errors were encountered: