You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Paulo Motta (Jira)" <ji...@apache.org> on 2022/03/08 16:15:00 UTC
[jira] [Commented] (CASSANDRA-16325) Update streaming metrics incrementally
[ https://issues.apache.org/jira/browse/CASSANDRA-16325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17503042#comment-17503042 ]
Paulo Motta commented on CASSANDRA-16325:
-----------------------------------------
Hi [~dgvozdenac]. Thanks for taking this up.
It seems like a similar issue happens with compaction metrics.
There was some code changes in these areas in recent versions. I think a good start would be to inspect the code in {{trunk}} to check where streaming and compaction size metrics are updated, and if they're being done incrementally or only at the end of the operation.
> Update streaming metrics incrementally
> --------------------------------------
>
> Key: CASSANDRA-16325
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16325
> Project: Cassandra
> Issue Type: Improvement
> Components: Observability/Metrics
> Reporter: Paulo Motta
> Assignee: Dejan Gvozdenac
> Priority: Normal
> Labels: lhf
>
> Currently the inbound and outbound streamed bytes metrics are incremented after each file is streamed, what doesn't represent the current number of bytes streamed since it can take a long time for a large file to be streamed. We should update the metric incrementally as data is streamed.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org