Nilotpal Nandi created HDDS-6417:
------------------------------------
Summary: balancer throws incorrect message on console when started
with wrong configs
Key: HDDS-6417
URL: https://issues.apache.org/jira/browse/HDDS-6417
Project: Apache Ozone
Issue Type: Bug
Components: Ozone CLI
Reporter: Nilotpal Nandi
Assignee: Nilotpal Nandi
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."
{noformat}
ozone admin containerbalancer stop
Stopping ContainerBalancer...
ozone admin containerbalancer start -d=100
Container Balancer is already running. Please stop it first.
{noformat}
{noformat}
2022-02-15 12:06:50,352 INFO SecurityLogger.org.apache.hadoop.ipc.Server: Auth
successful for [email protected] (auth:KERBEROS)
2022-02-15 12:06:50,355 INFO
SecurityLogger.org.apache.hadoop.security.authorize.ServiceAuthorizationManager:
Authorization successful for [email protected] (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.
{noformat}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]