You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Gargi Jaiswal (Jira)" <ji...@apache.org> on 2026/06/26 10:11:00 UTC
[jira] [Updated] (HDDS-15690) DiskBalancer status command fails when passing DataNode ID instead of address
[ https://issues.apache.org/jira/browse/HDDS-15690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gargi Jaiswal updated HDDS-15690:
---------------------------------
Summary: DiskBalancer status command fails when passing DataNode ID instead of address (was: ozone admin datanode diskbalancer status command fails when passing DataNode ID instead of address)
> DiskBalancer status command fails when passing DataNode ID instead of address
> -----------------------------------------------------------------------------
>
> Key: HDDS-15690
> URL: https://issues.apache.org/jira/browse/HDDS-15690
> Project: Apache Ozone
> Issue Type: Improvement
> Components: Ozone Datanode
> Affects Versions: 2.3.0
> Reporter: Arun Sarin
> Priority: Minor
>
> ozone admin datanode diskbalancer status command fails when passing DataNode ID instead of address
> Minor (Usability / CLI Consistency)
> The {{ozone admin datanode diskbalancer status}} command currently only accepts a DataNode's network address/host string. If a user attempts to pass a valid {{datanodeUuid}} (DataNode ID), the command fails or throws an unsupported/invalid argument error.
> For better usability and alignment with other {{ozone admin}} commands (which typically support both UUIDs and addresses to identify cluster nodes), this command should be updated to resolve and accept the DataNode ID.
> {code:java}
> [root@ccycloud-1.disk-balancer-cluster-15.root.comops.site ~]# ozone admin datanode list -id scm1
> Datanode: a3b63511-bdf8-4fa1-8ab6-d19c0e806f84 (/default/10.140.95.199/ccycloud-2.disk-balancer-cluster-15.root.comops.site/3 pipelines)
> Operational State: IN_SERVICE
> Health State: HEALTHY
> Total volume count: 1
> Healthy volume count: 1
> Related pipelines:
> 18acb50f-830d-426d-a8c4-a2d0577c12ab/RATIS/THREE/RATIS/OPEN/Follower
> 1f6743b3-3eb4-4c9b-994c-3655217dc9b4/RATIS/THREE/RATIS/OPEN/Leader
> f5ef1508-579a-4bee-9933-a04c525c36dd/RATIS/ONE/RATIS/OPEN/Leader
> Datanode: bc55ef13-ba30-4086-9f80-a5c9abc263ed (/default/10.140.181.1/ccycloud-7.disk-balancer-cluster-15.root.comops.site/3 pipelines)
> Operational State: IN_SERVICE
> Health State: HEALTHY
> Total volume count: 1
> Healthy volume count: 1
> Related pipelines:
> a5bf9a58-1eb2-4036-9e3a-c8e508942482/RATIS/THREE/RATIS/OPEN/Leader
> 85ef6b85-f3c1-4ce6-bd9d-8ada883a88fe/RATIS/ONE/RATIS/OPEN/Leader
> a2075c08-4167-462c-acb1-1bdf03cfc47a/RATIS/THREE/RATIS/OPEN/Follower
> Datanode: c557e715-f1ef-458b-8df0-04dc63b54e0e (/default/10.140.163.5/ccycloud-8.disk-balancer-cluster-15.root.comops.site/1 pipelines)
> Operational State: IN_SERVICE
> Health State: HEALTHY
> Total volume count: 1
> Healthy volume count: 1
> Related pipelines:
> 2e4b6954-f2be-47b4-bd68-0fa5c8bc4eca/RATIS/ONE/RATIS/OPEN/Leader {code}
> Now check the status of disk balancer
> {code:java}
> [root@ccycloud-1.disk-balancer-cluster-15.root.comops.site ~]# ozone admin datanode diskbalancer status a3b63511-bdf8-4fa1-8ab6-d19c0e806f84
> Error on node [a3b63511-bdf8-4fa1-8ab6-d19c0e806f84]: Invalid host name: local host is: "ccycloud-1.disk-balancer-cluster-15.root.comops.site/10.140.213.128"; destination host is: "a3b63511-bdf8-4fa1-8ab6-d19c0e806f84":19864; java.net.UnknownHostException: Invalid host name: local host is: "ccycloud-1.disk-balancer-cluster-15.root.comops.site/10.140.213.128"; destination host is: "a3b63511-bdf8-4fa1-8ab6-d19c0e806f84":19864; java.net.UnknownHostException; For more details see: http://wiki.apache.org/hadoop/UnknownHost; For more details see: http://wiki.apache.org/hadoop/UnknownHost
> Failed to get DiskBalancer status from nodes: [a3b63511-bdf8-4fa1-8ab6-d19c0e806f84] {code}
--
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