[
https://issues.apache.org/jira/browse/HDDS-8169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Siddhant Sangwan updated HDDS-8169:
-----------------------------------
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. (was: ContainerBalancer is a highly available
service. It's 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. )
> Delay Starting ContainerBalancer after SCM failover
> ---------------------------------------------------
>
> Key: HDDS-8169
> URL: https://issues.apache.org/jira/browse/HDDS-8169
> Project: Apache Ozone
> Issue Type: Sub-task
> Components: SCM
> Reporter: Siddhant Sangwan
> Assignee: Siddhant Sangwan
> Priority: Major
> Fix For: 1.4.0
>
>
> 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.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
