Gargi-jais11 opened a new pull request, #8610:
URL: https://github.com/apache/ozone/pull/8610

   ## What changes were proposed in this pull request?
   The DiskBalancerManager#getDiskBalancerStatus() method filters only healthy 
datanodes when querying all nodes, but returns all specified hosts regardless 
of their health. This inconsistency can lead to confusion or inaccurate 
monitoring.
   This JIRA proposes applying the same IN_SERVICE and HEALTHY filters for 
specific hosts to ensure consistent behavior.
   
   ## What is the link to the Apache JIRA
   https://issues.apache.org/jira/browse/HDDS-13212
   
   ## How was this patch tested?
   
   Tested manually on docker cluster.
   ```
   bash-5.1$ ozone admin datanode diskbalancer status -d ozone-ha-datanode-2 -d 
ozone-ha-datanode-3 -d  ozone-ha-datanode-1
   Status result:
   Datanode                            Status          Threshold(%)    
BandwidthInMB   Threads      SuccessMove  FailureMove  BytesMoved(MB)  
EstBytesToMove(MB) EstTimeLeft(min)
   ozone-ha-datanode-1.ozone-ha_default STOPPED         10.0000         10      
        5            0            0            0               0               
0              
   
   Note: Estimated time left is calculated based on the estimated bytes to move 
and the configured disk bandwidth.
   ```
   related logs 
   ```
   2025-06-12 10:55:11 2025-06-12 05:25:11,553 [IPC Server handler 14 on 
default port 9860] WARN node.DiskBalancerManager: Datanode 
ozone-ha-datanode-2.ozone-ha_default is not in optimal state for disk 
balancing. Operational state: ENTERING_MAINTENANCE
   2025-06-12 10:55:11 2025-06-12 05:25:11,553 [IPC Server handler 14 on 
default port 9860] WARN node.DiskBalancerManager: Datanode 
ozone-ha-datanode-3.ozone-ha_default is not in optimal state for disk 
balancing. Operational state: DECOMMISSIONING
   ```


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


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

Reply via email to