[
https://issues.apache.org/jira/browse/HDDS-14906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated HDDS-14906:
----------------------------------
Labels: pull-request-available (was: )
> Handle possible MoveResult by the MoveManager when running Balancer
> -------------------------------------------------------------------
>
> Key: HDDS-14906
> URL: https://issues.apache.org/jira/browse/HDDS-14906
> Project: Apache Ozone
> Issue Type: Bug
> Reporter: Aswin Shakil
> Assignee: Sarveksha Yeshavantha Raju
> Priority: Major
> Labels: pull-request-available
>
> If there is already a move that is happening we return
> {{{}FAIL_CONTAINER_ALREADY_BEING_MOVED{}}}, This {{MoveResult}} also skips
> adding the source datanode back to the queue. Along with HDDS-14614, We also
> need to fix this issue in a similar way.
> For {{REPLICATION_NOT_HEALTHY_AFTER_MOVE}} We need to exclude the container
> and still add the source datanode back to queue. The change would look
> something like this. Let me know if this makes sense.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
