You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Trying to establish a session with the Cassandra v5 cluster (inside the Docker container) using native protocol v5. I saw that the version 5 protocol was added already, but it seems it is not working properly for some reason. I've debugged the connection process and found that the error happened during the readHeader() function execution.
So, the process of connection according to logs looks like this:
I've compared the connection process using 5 version with 3 and 4 versions of the protocol. It seems pretty similar, except the one thing. When we use the 5 version the first byte always changes from 133 to 114. Now, I am reading the native protocol 5 specification to understand what changes should be made to fix the issue. Will be glad to receive any suggestions regarding it.
root@2e8cb70614b1:/# cqlsh
WARNING: cqlsh was built against 5.0-beta1, but this server is 5.0. All features may not work!
Connected to Test Cluster at 127.0.0.1:9042
[cqlsh 6.2.0 | Cassandra 5.0-beta1 | CQL spec 3.4.7 | Native protocol v5]
The text was updated successfully, but these errors were encountered:
Thank you, @martin-sucha. Will try to reflect new changes to support the v5 protocol for Cassandra in GoCQL. Do you have any suggestions on how to acquire the contributor role to be able to review and merge PRs?
What version of Cassandra are you using?
5
What version of Gocql are you using?
v1.6.0
What version of Go are you using?
go1.21.6 linux/amd64
What did you do?
Trying to establish a session with the Cassandra v5 cluster (inside the Docker container) using native protocol v5. I saw that the version 5 protocol was added already, but it seems it is not working properly for some reason. I've debugged the connection process and found that the error happened during the
readHeader()
function execution.So, the process of connection according to logs looks like this:
I've compared the connection process using 5 version with 3 and 4 versions of the protocol. It seems pretty similar, except the one thing. When we use the 5 version the first byte always changes from 133 to 114. Now, I am reading the native protocol 5 specification to understand what changes should be made to fix the issue. Will be glad to receive any suggestions regarding it.
Code snippet:
What did you expect to see?
Successfully established connection
What did you see instead?
Error from the gocql:
Cassandra logs:
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 output:
The text was updated successfully, but these errors were encountered: