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

Sreeja updated HDDS-15667:
--------------------------
    Description: 
Currently, when Container Balancer is stopped, `ozone admin containerbalancer 
status` only reports: "ContainerBalancer is Not Running."

After stop, status should show the last known run state:
 * Stop reason (also in non-verbose mode)
 * Start/stop timestamps, balancing duration, and configuration used ( with -v 
flag)
 * Last iteration details ( with -v flag)
 * Iteration history (with -v -H flag)

This improves observability and helps users understand the balancer's last 
execution without checking logs.

  was:
Currently, when Container Balancer is stopped, `ozone admin containerbalancer 
status` only reports: "ContainerBalancer is Not Running."

After stop, status should show the last known run state:
 * Stop reason (also in non-verbose mode)
 * Start/stop timestamps, balancing duration, and configuration used ( with -v 
flag)
 * Last iteration details ( with -v flag)
 * Iteration history (with -v -H flag)

This improves observability and helps users understand the balancer's last 
execution without checking logs. Last run info is available on the same SCM 
instance until restart.


> Enhance containerbalancer status --verbose to display detailed information 
> after Container Balancer stops
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: HDDS-15667
>                 URL: https://issues.apache.org/jira/browse/HDDS-15667
>             Project: Apache Ozone
>          Issue Type: Sub-task
>            Reporter: Sreeja
>            Assignee: Sreeja
>            Priority: Major
>
> Currently, when Container Balancer is stopped, `ozone admin containerbalancer 
> status` only reports: "ContainerBalancer is Not Running."
> After stop, status should show the last known run state:
>  * Stop reason (also in non-verbose mode)
>  * Start/stop timestamps, balancing duration, and configuration used ( with 
> -v flag)
>  * Last iteration details ( with -v flag)
>  * Iteration history (with -v -H flag)
> This improves observability and helps users understand the balancer's last 
> execution without checking logs.



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