You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ozone.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2023/02/27 13:02:00 UTC

[jira] [Updated] (HDDS-8034) Check container replication health before scheduling move in MoveManager

     [ https://issues.apache.org/jira/browse/HDDS-8034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

ASF GitHub Bot updated HDDS-8034:
---------------------------------
    Labels: pull-request-available  (was: )

> Check container replication health before scheduling move in MoveManager
> ------------------------------------------------------------------------
>
>                 Key: HDDS-8034
>                 URL: https://issues.apache.org/jira/browse/HDDS-8034
>             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#move already checks if a container has any in-flight (pending) Adds or Deletes before scheduling a move. However, there is some time between the replication thread checking the health of a container and the UnhealthyReplicationProcessor thread scheduling Adds and Deletes. To be safe, we should also check the container's health in MoveManager before scheduling move.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org