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

Wei-Chiu Chuang commented on HDDS-11341:
----------------------------------------

Much of this issue’s scope appears to have been implemented by HDDS-15352 ([PR 
#10337|https://github.com/apache/ozone/pull/10337]). The Datanode Decommission 
and Maintenance dashboard includes replication queues, inflight tasks, EC 
reconstruction command rates, supervisor task status and completion rates, and 
replicator byte-transfer rates and latency.

Some EC observability gaps remain:
* Datanode reconstruction totals and failure counters from 
{{ECReconstructionMetrics}}.
* Client reconstruction totals and failures from {{XceiverClientMetrics}}.
* SCM EC replica deletion, create/delete timeout, and partial reconstruction 
“none overloaded” counters.
* EC reconstruction bytes, in-progress tasks, and latency metrics requested in 
HDDS-17167.

Suggest reviewing the existing dashboard against this issue’s acceptance 
criteria, then either narrowing this issue to the remaining gaps or closing it 
and tracking those gaps in focused follow-up issues.

> Add Grafana dashboard for HDDS health and replication progress
> --------------------------------------------------------------
>
>                 Key: HDDS-11341
>                 URL: https://issues.apache.org/jira/browse/HDDS-11341
>             Project: Apache Ozone
>          Issue Type: Improvement
>          Components: Ozone Dashboards
>            Reporter: Ethan Rose
>            Priority: Major
>
> Add a Grafana dashboard to show information about datanode health, ongoing 
> and pending replication and reconstruction tasks, and the amount of data 
> being moved between nodes due to these tasks. This board will be useful to 
> monitor during disk failure, node failure, node decom, and maintenance.
> SCM replication manager likely has a lot of the metrics for ongoing tasks 
> already. We may need to add more metrics to datanodes to monitor tasks that 
> are ongoing (not just those that are queued) and the amount of data being 
> moved. I think some datanode command queue and handler related metrics are 
> unused as well and those can be checked/removed/updated as part of this PR.



--
This message was sent by Atlassian Jira
(v10.3.26#10030026)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to