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

Ethan Rose updated HDDS-11511:
------------------------------
    Description: 
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.

  was:
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.
* 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.


> 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
>            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]

Reply via email to