[HDDS-6417] balancer throws incorrect message on console when started with wrong configs

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: 1.3.0
• Component/s: Ozone CLI
• Labels: pull-request-available
• Assignee: Nilotpal Nandi
• Reporter: Nilotpal Nandi
• Created: 04/Mar/22 11:28
• Updated: 07/Mar/22 08:46
• Resolved: 07/Mar/22 08:46

Description

balancer is already stopped. But when started with wrong configs (here, hdds.container.balancer.balancing.iteration.interval was modified), it throws error "Container Balancer is already running. Please stop it first."

ozone admin containerbalancer stop
Stopping ContainerBalancer...
ozone admin containerbalancer start -d=100
Container Balancer is already running. Please stop it first.

 

2022-02-15 12:06:50,352 INFO SecurityLogger.org.apache.hadoop.ipc.Server: Auth successful for [e-mail] (auth:KERBEROS)
2022-02-15 12:06:50,355 INFO SecurityLogger.org.apache.hadoop.security.authorize.ServiceAuthorizationManager: Authorization successful for [e-mail] (auth:KERBEROS) for protocol=interface org.apache.hadoop.hdds.scm.protocol.StorageContainerLocationProtocol
2022-02-15 12:06:50,356 INFO org.apache.hadoop.hdds.scm.container.balancer.ContainerBalancer: balancing.iteration.interval should be larger than hdds.datanode.du.refresh.period.

Issue Links

• links to: GitHub Pull Request #3164