[jira] [Resolved] (HDDS-15491) [DiskBalancer] Preserve datanode order in status command output

["Gargi Jaiswal (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/HDDS-15491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gargi Jaiswal resolved HDDS-15491.
----------------------------------
    Resolution: Fixed

> [DiskBalancer] Preserve datanode order in status command output
> ---------------------------------------------------------------
>
>                 Key: HDDS-15491
>                 URL: https://issues.apache.org/jira/browse/HDDS-15491
>             Project: Apache Ozone
>          Issue Type: Sub-task
>          Components: Ozone CLI, Ozone Datanode
>            Reporter: Shilun Fan
>            Assignee: Shilun Fan
>            Priority: Major
>              Labels: pull-request-available
>
> The DiskBalancer status command executes requests in the order provided by the user, or in the order returned by SCM when --in-service-datanodes is used.
> However, the non-JSON status output currently stores successful responses in a ConcurrentHashMap and then builds the output from statuses.values(). ConcurrentHashMap does not guarantee iteration order, so the displayed status rows may not match the input datanode order or SCM returned order.
> This can make the command output harder to read and compare, especially when users provide multiple datanodes explicitly.
> The status command should preserve the successful datanode order when rendering non-JSON output.



--
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