[
https://issues.apache.org/jira/browse/HDDS-11511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17889755#comment-17889755
]
Ethan Rose commented on HDDS-11511:
-----------------------------------
Thanks for looking into this [~tejaskriya09]. It looks like most (maybe all?)
of the existing counter metrics above are totals since the cluster was last
restarted, not counts of how many were sent in just the last iteration. In
order to track the load the services are under, it will be easier to visualize
charting metrics that are set based only on the amount of work done in the last
iteration. We can have metrics for both total since restart and count from the
last iteration, but I think only the later will be used in HDDS-11512.
Some of these metrics deal with SCM to DN communication, like number of block
delete acks from DNs and number removed from the DB due to acks. We don't need
to worry about these right now since the primary task of this Jira and
HDDS-11512 is visualizing load of the deletion services. Since these are also
tracked in total since the last restart and there is no clear reset point like
another run of a service, they may be difficult to chart in a meaningful way.
> All deletion services should have consistent metrics
> ----------------------------------------------------
>
> Key: HDDS-11511
> URL: https://issues.apache.org/jira/browse/HDDS-11511
> Project: Apache Ozone
> Issue Type: Sub-task
> Reporter: Ethan Rose
> Assignee: Tejaskriya Madhan
> Priority: Major
>
> All background deletion services in Ozone should publish the same set of
> metrics for each thread:
> * Number of items handled in the last iteration
> ** For OM's directory deleting service, handling of files, empty dirs, and
> non-empty dirs may be tracked with different metrics.
> ** For services where one DB key is multiple blocks (key delete, SCM block
> transactions), a separate metric should exist for the number of blocks
> deleted in the iteration and the number of items processed.
> * Time spent in the last iteration
> Some services may already have these metrics, but some specifically in the OM
> do not. This Jira should review all the services and fill in these metrics
> where they are missing.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
