[jira] [Resolved] (HDDS-11640) Deletion services in SCM, OM and DN should have consistent metrics

["Tejaskriya Madhan (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/HDDS-11640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tejaskriya Madhan resolved HDDS-11640.
--------------------------------------
    Resolution: Done

> Deletion services in SCM, OM and DN should have consistent metrics
> ------------------------------------------------------------------
>
>                 Key: HDDS-11640
>                 URL: https://issues.apache.org/jira/browse/HDDS-11640
>             Project: Apache Ozone
>          Issue Type: Sub-task
>            Reporter: Tejaskriya Madhan
>            Assignee: Tejaskriya Madhan
>            Priority: Major
>              Labels: pull-request-available
>
> 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 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 of these metrics, 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: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org