You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Amal Sebastian (Jira)" <ji...@apache.org> on 2026/10/17 05:09:00 UTC
[jira] [Commented] (CASSANDRA-21091) Missing metrics with protocol v5
[ https://issues.apache.org/jira/browse/CASSANDRA-21091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18128069#comment-18128069 ]
Amal Sebastian commented on CASSANDRA-21091:
--------------------------------------------
[~dnk] [~samt] I saw that you two have worked in the v5 message handler code, so I wanted to ask for your eyes on this. The PR has been open since Sep 6 and hasn't had a review yet. I'd appreciate a look when you have time, and I'm happy to retarget branches if needed.
PR: [https://github.com/apache/cassandra/pull/5120]
> Missing metrics with protocol v5
> --------------------------------
>
> Key: CASSANDRA-21091
> URL: https://issues.apache.org/jira/browse/CASSANDRA-21091
> Project: Apache Cassandra
> Issue Type: Bug
> Reporter: Andy Salnikov
> Priority: Normal
>
> I am testing our client-side setup switching from protocol v4 to v5 and monitoring Cassandra metrics. What I see is that one particular metric is missing (or is 0) on server side when I switch to v5, metric is type=Client name=RequestSize.
> Server side is Cassandra 5.0.6 with Java 17. Client side is DataStax Python driver latest version. When I configure client to use protocol v4, then the above metric is generating reasonable values. When I switch protocol to v5, the metric shows zeros.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org