You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Dean Z (Jira)" <ji...@apache.org> on 2020/05/31 13:38:00 UTC
[jira] [Commented] (CASSANDRA-8612) Read metrics should be updated
on all types of reads
[ https://issues.apache.org/jira/browse/CASSANDRA-8612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17120541#comment-17120541 ]
Dean Z commented on CASSANDRA-8612:
-----------------------------------
Hi [~cnlwsu] , new to the community, trying to start with easy ones, not sure how this patch looks.[^0001-Update-read-metrics-on-all-types-of-reads.patch]
> Read metrics should be updated on all types of reads
> ----------------------------------------------------
>
> Key: CASSANDRA-8612
> URL: https://issues.apache.org/jira/browse/CASSANDRA-8612
> Project: Cassandra
> Issue Type: Improvement
> Components: Observability/Metrics
> Reporter: Chris Lohfink
> Priority: Low
> Labels: lhf, metrics
> Attachments: 0001-Update-read-metrics-on-all-types-of-reads.patch
>
>
> Metrics like "sstables per read" are not updated on a range slice. Although separating things out for each type of read could make sense like we do for latencies, only exposing the metrics for one type can be a little confusing when people do a query and see nothing increases. I think its sufficient to use the same metrics for all reads.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org