[HDDS-8169] Delay Starting ContainerBalancer after SCM failover

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Implemented
• Fix Version/s: 1.4.0
• Component/s: Balancer, SCM
• Labels: pull-request-available
• Target Version/s: 1.4.0
• Assignee: Siddhant Sangwan
• Reporter: Siddhant Sangwan
• Created: 15/Mar/23 12:14
• Updated: 05/May/23 15:22
• Resolved: 27/Mar/23 15:23

Description

ContainerBalancer is a highly available service. Its configurations are replicated using protobufs and persisted on each SCM in binary. It runs only in the leader SCM. Currently, there is no delay when ContainerBalancer starts running in the new leader. We should wait for some time for Datanodes to detect that there's been a leader change and expire commands from old leaders.

Issue Links

• is required by: HDDS-8170 Let ContainerBalancer consider EC containers for balancing
• links to: GitHub Pull Request #4458