You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Priyesh K (Jira)" <ji...@apache.org> on 2026/06/09 06:56:00 UTC
[jira] [Commented] (HDDS-14446) Make Datanode disk space related commands and metrics clear
[ https://issues.apache.org/jira/browse/HDDS-14446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18087540#comment-18087540 ]
Priyesh K commented on HDDS-14446:
----------------------------------
I can see PR associated with this already merged in 2.2.0. But ticket is not made resolved. So making ticket resolved.
> Make Datanode disk space related commands and metrics clear
> -----------------------------------------------------------
>
> Key: HDDS-14446
> URL: https://issues.apache.org/jira/browse/HDDS-14446
> Project: Apache Ozone
> Issue Type: Improvement
> Components: DN, Ozone Recon, SCM
> Affects Versions: 2.1.0
> Reporter: Siddhant Sangwan
> Assignee: Siddhant Sangwan
> Priority: Major
> Labels: pull-request-available
>
> Ozone currently exposes Datanode disk space statistics (capacity, used space, available space) at various places - Datanode Web UI overview page, JMX volume info metrics, SCM JMX metrics, usageinfo command, Recon Datanodes page, Recon main overview page.
> However, the terms used to shows these stats are currently confusing. For example, if Recon is showing the Capacity of a Datanode with 1 volume as 500 GB, that's actually the _capacity available to Ozone_. That is, raw disk capacity - du.reserved, not raw disk capacity.
> This jira aims to clarify these terms and make them consistent everywhere, except the main Recon overview page - that can be handled in a separate jira.
--
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