[CASSANDRA-14919] Regression in paging queries in mixed version clusters

• Type: Bug
• Status: Resolved
• Priority: Urgent
• Resolution: Fixed
• Fix Version/s: 3.0.18, 3.11.4
• Component/s: CQL/Interpreter, Messaging/Internode, Messaging/Thrift
• Bug Category: Availability - Unavailable
• Severity: Critical
• Complexity: Challenging
• Discovered By: Unit Test
• Since Version: 3.0.0
• Assignee: Sam Tunnicliffe
• Reporter: Sam Tunnicliffe

Authors

Sam Tunnicliffe

Reviewers

Benedict Elliott Smith

• Created: 04/Dec/18 10:24
• Updated: 02/Aug/19 03:00
• Resolved: 06/Dec/18 16:18

Description

The changes to handling legacy bounds in CASSANDRA-14568/CASSANDRA-14749/CASSANDRA-14912 break paging queries where the coordinator is a legacy node and the replica is an upgraded node.

The long-held assumption made by LegacyLayout::decodeBound that "There can be more components than the clustering size only in the case this is the bound of a collection range tombstone." is not true as serialized paged read commands may also include these type of bounds in their SliceQueryFilter. The additional checks the more recent tickets add cause such queries to error when processed by a 3.0 replica.