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

Ashish Kumar resolved HDDS-16179.
---------------------------------
    Fix Version/s: 2.3.0
       Resolution: Implemented

> Estimate command for container balancer with profiles
> -----------------------------------------------------
>
>                 Key: HDDS-16179
>                 URL: https://issues.apache.org/jira/browse/HDDS-16179
>             Project: Apache Ozone
>          Issue Type: Sub-task
>            Reporter: Sreeja Chintalapati
>            Assignee: Sreeja Chintalapati
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 2.3.0
>
>
> h2. Problem
> Today, users can start the container balancer with {{{}ozone admin 
> containerbalancer start{}}}, but there is no way to preview:
>  * how much data needs to be moved
>  * how long balancing may take
>  * how different throttling settings affect throughput and duration
> This makes it hard to plan maintenance windows or choose safe balancer 
> settings without trial and error.
> h2. Proposed Solution
> Add {{ozone admin containerbalancer estimate}} that:
>  # Fetches live datanode usage from SCM
>  # Reads balancer limits, timeouts from local balancer configuration (with 
> optional CLI overrides)
>  # Reads profile presets from ContainerBalancerProfile enum
>  # Estimates, per profile:
>  ** bytes to move
>  ** per-iteration throughput
>  ** estimated iterations
>  ** upper-bound duration (with a +30% planning buffer)
> Introduces SLOW, MEDIUM, and FAST throttling profiles in 
> ContainerBalancerProfile enum with presets for datanode involvement and 
> per-node move limits.
> Add {{ContainerBalancerAdvisor}} to centralize cluster analysis, estimation, 
> and validation logic used by estimate subcommand.



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