[
https://issues.apache.org/jira/browse/CASSANDRA-16354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sam Tunnicliffe updated CASSANDRA-16354:
----------------------------------------
Status: Ready to Commit (was: Review In Progress)
+1 on the dtest change (which I think we'll need to duplicate for the actual
upgrade tests for CASSANDRA-16347)
> python dtest fails to talk to 2.2 using protocol 4 but cqlsh has no issue
> -------------------------------------------------------------------------
>
> Key: CASSANDRA-16354
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16354
> Project: Cassandra
> Issue Type: Bug
> Components: CI, Test/dtest/python
> Reporter: David Capwell
> Assignee: Adam Holmberg
> Priority: Normal
> Fix For: 4.0-beta
>
>
> https://app.circleci.com/pipelines/github/dcapwell/cassandra/850/workflows/79486fdd-06d0-4d04-aa32-0fa648182356/jobs/5019/artifacts
> We see that upgrade tests which talk to 2.2 clusters fail with the following
> error
> {code}
> > ???
> E cassandra.cluster.NoHostAvailable: ('Unable to connect to any servers',
> {'127.0.0.1:9042': DriverException('ProtocolError returned from server while
> using explicitly set client protocol_version 4',)})
> {code}
> For some reason, setting protocol version 4 causes 2.2 to fail, but this does
> not happen when using cqlsh (from trunk)
> {code}
> ./bin/cqlsh --protocol-version=4
> Connected to Test Cluster at 127.0.0.1:9042.
> [cqlsh 5.0.1 | Cassandra 2.2.20-SNAPSHOT | CQL spec 3.3.1 | Native protocol
> v4]
> Use HELP for help.
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
