[
https://issues.apache.org/jira/browse/CASSANDRA-16474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sam Tunnicliffe updated CASSANDRA-16474:
----------------------------------------
Bug Category: Parent values: Availability(12983)Level 1 values: Response
Crash(12991)
Complexity: Normal
Discovered By: Unit Test
Fix Version/s: 4.0-beta
Severity: Normal
Status: Open (was: Triage Needed)
Candidate driver patch has been produced, running CI now.
* [Circle
JDK8|https://app.circleci.com/pipelines/github/beobal/cassandra/238/workflows/1e121554-3514-4840-a919-d785ee0484f5]
* [Circle
JDK11|https://app.circleci.com/pipelines/github/beobal/cassandra/238/workflows/cfc78f97-0700-4e77-853c-411d90dbb11d]
*
[ci-c.apache.org|https://ci-cassandra.apache.org/view/patches/job/Cassandra-devbranch/444/]
> 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
> Fix For: 4.0-beta
>
>
> 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]
