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

Gargi Jaiswal updated HDDS-15441:
---------------------------------
        Parent: HDDS-15445
    Issue Type: Sub-task  (was: Improvement)

> [DiskBalancer] Fix DiskBalancer documentation inconsistencies
> -------------------------------------------------------------
>
>                 Key: HDDS-15441
>                 URL: https://issues.apache.org/jira/browse/HDDS-15441
>             Project: Apache Ozone
>          Issue Type: Sub-task
>            Reporter: Shilun Fan
>            Assignee: Shilun Fan
>            Priority: Minor
>              Labels: pull-request-available
>
> The DiskBalancer feature documentation has several inconsistencies with the 
> current implementation.
> Issues found in the English and Chinese DiskBalancer docs:
> 1. Feature flag enablement example is incorrect.
>    The text says DiskBalancer can be enabled by setting the property to true, 
> but the example shows:
>    hdds.datanode.disk.balancer.enabled = false
> 2. The documented default value of --parallel-thread is inconsistent with the 
> code.
>    DiskBalancerConfiguration uses a default value of 5 for 
> hdds.datanode.disk.balancer.parallel.thread, but the command option table 
> says the default is 1.
> 3. The --container-states example includes OPEN,CLOSED.
>    OPEN is rejected by DiskBalancerConfiguration validation because 
> open-to-write container states are not movable. The example should use valid 
> movable states such as CLOSED or CLOSED,QUASI_CLOSED.
> 4. The Chinese documentation has the same issues.
>    It also documents --stop-after-disk-even default as false, while the 
> current default is true.
> 5. The Chinese configuration table contains an extra table separator in the 
> hdds.datanode.disk.balancer.enabled row, which breaks table formatting.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

Reply via email to