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

Sreeja Chintalapati reassigned HDDS-16181:
------------------------------------------

    Assignee: Sravani Revuri  (was: Sreeja Chintalapati)

> Add container balancer recommend CLI command to suggest config values for 
> slow/medium/fast profiles
> ---------------------------------------------------------------------------------------------------
>
>                 Key: HDDS-16181
>                 URL: https://issues.apache.org/jira/browse/HDDS-16181
>             Project: Apache Ozone
>          Issue Type: Sub-task
>            Reporter: Sreeja Chintalapati
>            Assignee: Sravani Revuri
>            Priority: Major
>
> Add ozone admin containerbalancer recommend command
> The command should:
>  # Fetch live datanode usage from SCM (via the existing getDatanodeUsageInfo 
> RPC)
>  # Read local Ozone configuration for global defaults (threshold, timeouts, 
> move limits etc.)
>  # Analyze the cluster using existing {{ContainerBalancerClusterAnalyzer}} / 
> {{ContainerBalancerClusterSnapshot}} (HDDS-16173)
>  # For each profile (SLOW, MEDIUM, FAST), produce:
>  ** Recommended configuration parameters with a short rationale
>  ** Time/iteration estimates by reusing 
> {{ContainerBalancerAdvisor.estimateDryRun()}} (HDDS-16179)
>  ** Each recommended values should be validated first.
> No --profile, config overrides, or interactive mode on this command
> If the user wants custom inputs or refined estimates, they use dry-run 
> instead.
> But the command should allow the user to provide include/exclude datanodes 
> and threshold values.
> {panel:title=Example output:}
> RECOMMENDED CONFIGURATION (profile: SLOW)
>  ══════════════════════════════════════════════════════
>   Parameter                                                          Value    
>                   Rationale
>   ─────────────────────────────────────────────────────
>   --threshold                                                         <value> 
>                 <why this value>
>   --max-datanodes-percentage-to-involve       <value>                 <why 
> this value>
>   --max-size-to-move-per-iteration-in-gb        <value>                 <why 
> this value>
>   --max-size-entering-target-in-gb                   <value>                  
> <why this value>
>   --max-size-leaving-source-in-gb                   <value>                  
> <why this value>
>   --move-timeout-minutes                                 <value>              
>      <why this value>
>   --move-replication-timeout-minutes             <value>                    
> <why this value>
>   --balancing-iteration-interval-minutes          <value>                    
> <why this value>
>   --iterations                                                        <value> 
>                    <why this value>
>  ─── Estimation ─────────────────────────────────────────────
>   Bytes to move:                              <cluster-derived>
>   Per iteration (estimate):               <estimate>
>   Estimated iterations:                    <N>(planning estimate: <M>, 
> includes +30% buffer)
>   Estimated duration:                     upper bound <N> (planning estimate: 
> <M>, includes +30% buffer)
>                                                         (assumes full move 
> timeout + interval each cycle)
> (profile: MEDIUM)
>  ...
> (profile: FAST)
>  ...
> {panel}
>  
>  



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