You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jakub Zytka (Jira)" <ji...@apache.org> on 2024/02/08 13:12:00 UTC
[jira] [Comment Edited] (CASSANDRA-19379) Range queries performed with NODE_LOCAL update read request metrics instead of range request metrics
[ https://issues.apache.org/jira/browse/CASSANDRA-19379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17815670#comment-17815670 ]
Jakub Zytka edited comment on CASSANDRA-19379 at 2/8/24 1:11 PM:
-----------------------------------------------------------------
Same problem with casWrite metricsĀ
was (Author: jakubzytka):
Same problem with casRead and casWrite metricsĀ
> Range queries performed with NODE_LOCAL update read request metrics instead of range request metrics
> ----------------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-19379
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19379
> Project: Cassandra
> Issue Type: Bug
> Reporter: Jakub Zytka
> Priority: Normal
>
> Queries like {{SELECT * FROM foo.bar}} update regular read metrics when executed with CL.NODE_LOCAL instead of range metrics (what happens with other CL).
> I understand that NODE_LOCAL is different, but I still think it's better to update range metrics for consistency's sake.
> This was not fixed in -- CASSANDRA-17052{-}, but I assume this was an accidental omission, not a conscious decision (at least the ticket doesn't mention{-} that).
> Actually, the test in CASSANDRA-17052 does explicitly expect bumping read metrics rather than range metrics.
> [~aleksey] , [~ifesdjeen] could you please weigh in on that?
--
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