[ https://issues.apache.org/jira/browse/CASSANDRA-16581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17344800#comment-17344800 ]
David Capwell commented on CASSANDRA-16581: ------------------------------------------- What I see is org.apache.cassandra.transport.InitialConnectionHandler#decode gets "firstByte" to be 66, and applying the PROTOCOL_VERSION_MASK doesn't change the value. When I run {code} ./bin/cqlsh --protocol-version 4 {code} the first byte is 4 and versionNum is also 4 (the same is true with --protocol-version 3, but first byte is 3) This looks like cqlsh is missing this? > 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 > Priority: Normal > Fix For: 3.0.x, 3.11.x, 4.0-rc > > > 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 message was sent by Atlassian Jira (v8.3.4#803005) --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org