[CASSANDRA-16474] Multiple python dtest failures after promoting protocol v5 from beta

• Type: Bug
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 4.0-rc1, 4.0
• Component/s: Messaging/Client
• Labels: protocolv5
• Bug Category: Availability - Response Crash
• Severity: Normal
• Complexity: Normal
• Discovered By: Unit Test
• Platform: All
• Since Version: 4.0-beta4

Source Control Link

https://github.com/apache/cassandra/commit/bad17a891a6df23f1e7698dc1285d031d0900118

Test and Documentation Plan

Full CI runs completed, follow up with smaller test runs targetting cql/cqlsh.

• Assignee: Sam Tunnicliffe
• Reporter: Sam Tunnicliffe

Authors

Sam Tunnicliffe

Reviewers

Adam Holmberg

• Created: 02/Mar/21 16:34
• Updated: 05/Mar/21 16:56
• Resolved: 04/Mar/21 14:53

Description

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).