[
https://issues.apache.org/jira/browse/HDDS-11511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17887502#comment-17887502
]
Tejaskriya Madhan edited comment on HDDS-11511 at 10/8/24 7:27 AM:
-------------------------------------------------------------------
Currently, these are the metrics present:
h2. OM
Metrics class: {{no metrics present}}
Deleting service classes: {{AbstractKeyDeletingService, }}
{{DirectoryDeletingService, }} {{KeyDeletingService, }}
{{SnapshotDeletingService}}
h2. SCM
metrics class : {{ScmBlockDeletingServiceMetrics}}
Deleting service class: {{SCMBlockDeletingService}}
Metrics present:
{code:java}
The number of individual delete transaction commands sent to all DN.
The number of ACK of delete transaction commands: success, failure
The number of individual delete transactions sent to all DN.
The number of delete transactions : success, failure
The number of completed txs which are removed from DB.
The number of created txs which are added into DB. {code}
h2. DN
Metrics class: {{BlockDeletingServiceMetrics}}
Deleting service classes: {{BlockDeletingService}}
Metrics present:
{code:java}
The number of delete blocks : success, failure
The total number of blocks: received to be processed, marked count, chosen to
be deleted, pending for processing
The total bytes for blocks successfully deleted.
The total number of DeleteBlockTransaction: received, that is a retry
transaction, failed due to container lock timeout, is out of order
The total number of Container: received to be processed, chosen to be
deleted{code}
The following metrics can be added to OM, SCM and DN:
{code:java}
The time spent in an iteration{code}
Additionally, for OM, as mentioned in the description, these metrics can be
introduced:
{code:java}
No. of items handled.
No. of keys sent to scm for deleteBlocks
No. of keys for which purgeKeyRequest is sent
No. of keys deleted in OM after SCM ack {code}
Are there any other metrics
was (Author: JIRAUSER298878):
Currently, these are the metrics present:
h2. OM
Metrics class: {{no metrics present}}
Deleting service classes: {{AbstractKeyDeletingService, }}
{{DirectoryDeletingService, }} {{KeyDeletingService, }}
{{SnapshotDeletingService}}
h2. SCM
metrics class : {{ScmBlockDeletingServiceMetrics}}
Deleting service class: {{SCMBlockDeletingService}}
Metrics present:
{code:java}
The number of individual delete transaction commands sent to all DN.
The number of ACK of delete transaction commands: success, failure
The number of individual delete transactions sent to all DN.
The number of delete transactions : success, failure
The number of completed txs which are removed from DB.
The number of created txs which are added into DB. {code}
{{{}{}}}{{{}{}}}
h2. DN
Metrics class: {{BlockDeletingServiceMetrics}}
Deleting service classes: {{BlockDeletingService}}
Metrics present:
{code:java}
The number of delete blocks : success, failure
The total number of blocks: received to be processed, marked count, chosen to
be deleted, pending for processing
The total bytes for blocks successfully deleted.
The total number of DeleteBlockTransaction: received, that is a retry
transaction, failed due to container lock timeout, is out of order
The total number of Container: received to be processed, chosen to be
deleted{code}
The following metrics can be added to OM, SCM and DN:
{code:java}
The time spent in an iteration{code}
Additionally, for OM, as mentioned in the description, these metrics can be
introduced:
{code:java}
No. of items handled.
No. of keys sent to scm for deleteBlocks
No. of keys for which purgeKeyRequest is sent
No. of keys deleted in OM after SCM ack {code}
Are there any other metrics
> 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]
