[
https://issues.apache.org/jira/browse/CASSANDRA-18030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brandon Williams updated CASSANDRA-18030:
-----------------------------------------
Resolution: Invalid
Status: Resolved (was: Triage Needed)
This jira is for the development of Apache Cassandra and as such makes for a
poor support vehicle. It is instead recommended to contact the community
through slack or the ML: https://cassandra.apache.org/_/community.html
> Few nodes in cassandra 3.11 cluster is unable to connect to v4 protocol
> version
> -------------------------------------------------------------------------------
>
> Key: CASSANDRA-18030
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18030
> Project: Cassandra
> Issue Type: Bug
> Reporter: sainath vadyala
> Priority: Urgent
>
> We have a Apache Cassandra cluster with 36 nodes running on k8s, cqlsh client
> was installed in a separate namespace. cqlsh is downgrading version from v4
> to v3 on some of the nodes but we have a case where all the nodes need to
> connect to v4, this is a requirement to set UNSET for avoiding null values to
> be converted to tombstones (only v4 is supported).
> {code:java}
> cqlsh 10.1.2.3 --ssl --protocol-version=3
> Connected to production at 10.1.2.3:9042.
> [cqlsh 5.0.1 | Cassandra 3.11.5 | CQL spec 3.4.4 | Native protocol v3]
> Use HELP for help.
> cqlsh>
> cqlsh 10.1.2.3 --ssl --protocol-version=4
> Connection error: ('Unable to connect to any servers', {'10.1.2.3':
> DriverException('ProtocolError returned from server while using explicitly
> set client protocol_version 4',)}) {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
