HDDS-13212. [DiskBalancer] Fix Inconsistent Health Check in DiskBalancer Status for Specific Hosts

[Gargi-jais11]

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. NodeStatus: ENTERING_MAINTENANCE(expiry: 1749816487s)-HEALTHY
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. NodeStatus: DECOMMISSIONING(no expiry)-HEALTHY

[github-actions]

No such command. gemini Available commands:

• /close : Close pending pull request temporary
• /help : Show all the available comment commands
• /label : add new label to the issue: /label <label>
• /pending : Add a REQUESTED_CHANGE type review to mark issue non-mergeable: /pending <reason>
• /ready : Dismiss all the blocking reviews by github-actions bot
• /retest : provide help on how to trigger new CI build

[Gargi-jais11]

/gemini review

[github-actions]

No such command. gemini Available commands:

• /close : Close pending pull request temporary
• /help : Show all the available comment commands
• /label : add new label to the issue: /label <label>
• /pending : Add a REQUESTED_CHANGE type review to mark issue non-mergeable: /pending <reason>
• /ready : Dismiss all the blocking reviews by github-actions bot
• /retest : provide help on how to trigger new CI build

[peterxcli]

Thanks @Gargi-jais11 for updating the patch and sorry for too many rounds of review.

[Gargi-jais11]

Thanks @Gargi-jais11 for updating the patch and sorry for too many rounds of review.

No issue. It's completly alright.

[Gargi-jais11]

@peterxcli Now you can review the patch with updated intergation test.

[peterxcli]

@Gargi-jais11 please fix the findbugs failure

[peterxcli]

Thanks @Gargi-jais11 for updating the patch, other LGTM!