[
https://issues.apache.org/jira/browse/HDDS-8168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Attila Doroszlai resolved HDDS-8168.
------------------------------------
Resolution: Implemented
> Make deadlines inside MoveManager for move commands configurable
> ----------------------------------------------------------------
>
> Key: HDDS-8168
> URL: https://issues.apache.org/jira/browse/HDDS-8168
> Project: Apache Ozone
> Issue Type: Sub-task
> Components: SCM
> Reporter: Siddhant Sangwan
> Assignee: Siddhant Sangwan
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.4.0
>
>
> MoveManager currently has a hardcoded deadline of 60 minutes. We should make
> this configurable, and that configuration should be present in
> ContainerBalancerConfiguration.
> Move is replication + deletion. Replication involves copying between two
> datanodes so it's generally more expensive than deletion. So we probably need
> to have an additional configuration for deciding how much time out of the
> total move deadline is allowed for replication. The rest will be allowed for
> deletion. Move deadline's configuration is
> "hdds.container.balancer.move.timeout".
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
