David Capwell created CASSANDRA-16581:
-----------------------------------------
Summary: Failure to execute queries should emit a KPI other than
read timeout/unavailable so it can be alerted/tracked
Key: CASSANDRA-16581
URL: https://issues.apache.org/jira/browse/CASSANDRA-16581
Project: Cassandra
Issue Type: Bug
Components: Messaging/Client, Observability/Metrics
Reporter: David Capwell
Assignee: David Capwell
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. This is also an issue
with 3.0 to 4.0 upgrade as clients attempting to speak v5 to a 3.x node will
hit the same issue
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
