[
https://issues.apache.org/jira/browse/CASSANDRA-16474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sam Tunnicliffe updated CASSANDRA-16474:
----------------------------------------
Fix Version/s: (was: 4.0-beta)
4.0
4.0-beta5
Since Version: 4.0-beta4
Source Control Link:
https://github.com/apache/cassandra/commit/bad17a891a6df23f1e7698dc1285d031d0900118
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
Thanks all, committed (the docker change only) to 2.2 in
{{bad17a891a6df23f1e7698dc1285d031d0900118}} and merged upwards, adding the
bundled driver update in trunk.
> Multiple python dtest failures after promoting protocol v5 from beta
> --------------------------------------------------------------------
>
> Key: CASSANDRA-16474
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16474
> Project: Cassandra
> Issue Type: Bug
> Components: Messaging/Client
> Reporter: Sam Tunnicliffe
> Assignee: Sam Tunnicliffe
> Priority: Normal
> Labels: protocolv5
> Fix For: 4.0-beta5, 4.0
>
>
> After making v5 the default for connections where a preferred protocol
> version is not specified, a number of python dtests are failing in CI
> environments.
> The issue appears to be with how the driver handles cases where the bytes
> read from the client socket doesn't constitute a complete frame (or to be
> more specific, the read buffer is exhausted whilst in the middle of reading a
> frame).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
