[CASSANDRA-16581] Failure to execute queries should emit a KPI other than read timeout/unavailable so it can be alerted/tracked

• Type: Bug
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 3.0.25, 3.11.11, 4.0-rc2, 4.0
• Component/s: Messaging/Client, Observability/Metrics
• Bug Category: Availability - Unavailable
• Severity: Normal
• Complexity: Low Hanging Fruit
• Discovered By: User Report
• Platform: All
• Since Version: NA

Source Control Link

https://github.com/apache/cassandra/commit/9c50b1f9a12a95b55851cc52d4b66440f9fafaea

Test and Documentation Plan

added tests

• Assignee: David Capwell
• Reporter: David Capwell

Authors

David Capwell

Reviewers

Sam Tunnicliffe

• Created: 08/Apr/21 22:15
• Updated: 04/Jun/21 11:01
• Resolved: 02/Jun/21 03:56

Description

When we are unable to parse a message we do not have a way to detect this from a monitoring point of view so can get into situations where we believe the database is fine but the clients are on-fire. This case popped up in the 2.1 to 3.0 upgrade as paging state wasn’t mixed-mode safe.

Issue Links

• links to: Circle CI: trunk
• links to: GH Branch: 3.0
• links to: GH Branch: 3.11
• links to: GH Branch: 4.0
• links to: GH Branch: python dtest trunk
• links to: GH Branch: trunk