Nilotpal Nandi created HDDS-6976:
------------------------------------

             Summary: 0G data moved by container balancer after successful 
iteration
                 Key: HDDS-6976
                 URL: https://issues.apache.org/jira/browse/HDDS-6976
             Project: Apache Ozone
          Issue Type: Bug
          Components: SCM
            Reporter: Nilotpal Nandi


steps taken :
-------------
1. Write 40GB of data on 5 DNs, Run container balancer using CLI, balancer went 
in running state.
2. Run SCM failover.
3. New leader election happened and container balancer started again.

Logs in new SCM leader shows that only 0GB moved.

scm logĀ 
{noformat}
Container Balancer status:
Container Balancer Configuration values:
2022-06-17 11:03:15,603 INFO 
org.apache.hadoop.hdds.scm.container.balancer.ContainerBalancer: Starting 
ContainerBalancer in this scm on status change
2022-06-17 11:03:15,606 INFO 
org.apache.hadoop.hdds.scm.container.balancer.ContainerBalancer: Starting 
Container Balancer...
Container Balancer status:
Container Balancer Configuration values:
2022-06-17 11:03:15,612 INFO 
org.apache.hadoop.hdds.scm.container.balancer.ContainerBalancer: Container 
Balancer has identified 3 Over-Utilized and 2 Under-Utilized Datanodes that 
need to be balanced.
2022-06-17 11:03:15,618 INFO 
org.apache.hadoop.hdds.scm.container.balancer.ContainerBalancer: 
ContainerBalancer matched source datanode 160b0324-2ce8-4f24-a5a2-e63fcc59073c 
with target datanode bde02c7a-3693-4a65-8227-d655943591c2 for container move.
2022-06-17 11:03:15,618 INFO 
org.apache.hadoop.hdds.scm.container.balancer.ContainerBalancer: 
ContainerBalancer is trying to move container #1003 from source datanode 
160b0324-2ce8-4f24-a5a2-e63fcc59073c to target datanode 
bde02c7a-3693-4a65-8227-d655943591c2
2022-06-17 11:03:15,643 INFO 
org.apache.hadoop.hdds.scm.container.balancer.ContainerBalancer: 
ContainerBalancer matched source datanode 160b0324-2ce8-4f24-a5a2-e63fcc59073c 
with target datanode bde02c7a-3693-4a65-8227-d655943591c2 for container move.
2022-06-17 11:03:15,643 INFO 
org.apache.hadoop.hdds.scm.container.balancer.ContainerBalancer: 
ContainerBalancer is trying to move container #4 from source datanode 
160b0324-2ce8-4f24-a5a2-e63fcc59073c to target datanode 
bde02c7a-3693-4a65-8227-d655943591c2
2022-06-17 11:03:15,655 INFO 
org.apache.hadoop.hdds.scm.container.balancer.ContainerBalancer: 
ContainerBalancer matched source datanode 160b0324-2ce8-4f24-a5a2-e63fcc59073c 
with target datanode bde02c7a-3693-4a65-8227-d655943591c2 for container move.
2022-06-17 11:03:15,655 INFO 
org.apache.hadoop.hdds.scm.container.balancer.ContainerBalancer: 
ContainerBalancer is trying to move container #1005 from source datanode 
160b0324-2ce8-4f24-a5a2-e63fcc59073c to target datanode 
bde02c7a-3693-4a65-8227-d655943591c2
2022-06-17 11:03:15,662 INFO 
org.apache.hadoop.hdds.scm.container.balancer.ContainerBalancer: 
ContainerBalancer matched source datanode 160b0324-2ce8-4f24-a5a2-e63fcc59073c 
with target datanode bde02c7a-3693-4a65-8227-d655943591c2 for container move.
2022-06-17 11:03:15,662 INFO 
org.apache.hadoop.hdds.scm.container.balancer.ContainerBalancer: 
ContainerBalancer is trying to move container #3 from source datanode 
160b0324-2ce8-4f24-a5a2-e63fcc59073c to target datanode 
bde02c7a-3693-4a65-8227-d655943591c2
2022-06-17 11:03:15,669 INFO 
org.apache.hadoop.hdds.scm.container.balancer.ContainerBalancer: 
ContainerBalancer matched source datanode 160b0324-2ce8-4f24-a5a2-e63fcc59073c 
with target datanode bde02c7a-3693-4a65-8227-d655943591c2 for container move.
2022-06-17 11:03:15,669 INFO 
org.apache.hadoop.hdds.scm.container.balancer.ContainerBalancer: 
ContainerBalancer is trying to move container #1 from source datanode 
160b0324-2ce8-4f24-a5a2-e63fcc59073c to target datanode 
bde02c7a-3693-4a65-8227-d655943591c2
2022-06-17 11:03:15,676 INFO 
org.apache.hadoop.hdds.scm.container.balancer.ContainerBalancer: 
ContainerBalancer matched source datanode 160b0324-2ce8-4f24-a5a2-e63fcc59073c 
with target datanode daf9bc99-d66d-443e-82de-2e837ac130b2 for container move.
2022-06-17 11:03:15,676 INFO 
org.apache.hadoop.hdds.scm.container.balancer.ContainerBalancer: 
ContainerBalancer is trying to move container #1002 from source datanode 
160b0324-2ce8-4f24-a5a2-e63fcc59073c to target datanode 
daf9bc99-d66d-443e-82de-2e837ac130b2
2022-06-17 11:03:15,681 INFO 
org.apache.hadoop.hdds.scm.container.balancer.ContainerBalancer: 
ContainerBalancer matched source datanode 160b0324-2ce8-4f24-a5a2-e63fcc59073c 
with target datanode daf9bc99-d66d-443e-82de-2e837ac130b2 for container move.
2022-06-17 11:03:15,681 INFO 
org.apache.hadoop.hdds.scm.container.balancer.ContainerBalancer: 
ContainerBalancer is trying to move container #1001 from source datanode 
160b0324-2ce8-4f24-a5a2-e63fcc59073c to target datanode 
daf9bc99-d66d-443e-82de-2e837ac130b2
2022-06-17 11:03:15,690 INFO 
org.apache.hadoop.hdds.scm.container.balancer.ContainerBalancer: 
ContainerBalancer matched source datanode 160b0324-2ce8-4f24-a5a2-e63fcc59073c 
with target datanode daf9bc99-d66d-443e-82de-2e837ac130b2 for container move.
2022-06-17 11:03:15,690 INFO 
org.apache.hadoop.hdds.scm.container.balancer.ContainerBalancer: 
ContainerBalancer is trying to move container #2 from source datanode 
160b0324-2ce8-4f24-a5a2-e63fcc59073c to target datanode 
daf9bc99-d66d-443e-82de-2e837ac130b2
2022-06-17 11:03:15,705 INFO 
org.apache.hadoop.hdds.scm.container.balancer.FindSourceGreedy: no more 
candidate source data node
2022-06-17 11:05:12,912 INFO 
org.apache.hadoop.hdds.scm.container.balancer.ContainerBalancer: Number of 
datanodes involved in this iteration: 3. Size moved in this iteration: 0GB.
2022-06-17 11:05:12,912 INFO 
org.apache.hadoop.hdds.scm.container.balancer.ContainerBalancer: Result of this 
iteration of Container Balancer: ITERATION_COMPLETED
{noformat}



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