[jira] [Commented] (HDDS-7703) Add num of datanodes metrics in ScmBlockDeletingServiceMetrics

["Sumit Agrawal (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/HDDS-7703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17764231#comment-17764231 ] 

Sumit Agrawal commented on HDDS-7703:
-------------------------------------

[~Symious] There is already a metrics which can provide the value,

@Metric(about = "The number of individual delete transaction commands sent " +
"to all DN.")
private MutableCounterLong numBlockDeletionCommandSent;

 

// This metrics keeps increasing when a command is send, so based on value change, can identify DNs command send every iteration.

We do not need another metrics to tell number of command send in last iteration, above will meet the target requried.

> Add num of datanodes metrics in ScmBlockDeletingServiceMetrics
> --------------------------------------------------------------
>
>                 Key: HDDS-7703
>                 URL: https://issues.apache.org/jira/browse/HDDS-7703
>             Project: Apache Ozone
>          Issue Type: Improvement
>            Reporter: Janus Chow
>            Assignee: Janus Chow
>            Priority: Major
>              Labels: pull-request-available
>
> SCM sends delete block commands to different datanodes. 
> There is a chance that one datanode has some issue handling the requests, and SCM will be sending all requests to the same datanode. 
> This metrics should be helpful to notice this issue.



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