[
https://issues.apache.org/jira/browse/CASSANDRA-21091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18128400#comment-18128400
]
Amal Sebastian commented on CASSANDRA-21091:
--------------------------------------------
[~dnk] Reworked per review on the PR: the gauge now sums each v5 connection's
queued bytes on read instead of adding a counter on the request path. v4 is
unchanged.
> 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
> Time Spent: 20m
> Remaining Estimate: 0h
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
