You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Attila Doroszlai (Jira)" <ji...@apache.org> on 2023/07/18 10:43:00 UTC

[jira] [Resolved] (HDDS-9019) ECUnderReplicationHandler rejects a potential target if it doesn't satisfy placement policy

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

Attila Doroszlai resolved HDDS-9019.
------------------------------------
    Fix Version/s: 1.4.0
       Resolution: Fixed

> ECUnderReplicationHandler rejects a potential target if it doesn't satisfy placement policy
> -------------------------------------------------------------------------------------------
>
>                 Key: HDDS-9019
>                 URL: https://issues.apache.org/jira/browse/HDDS-9019
>             Project: Apache Ozone
>          Issue Type: Bug
>          Components: ECOfflineRecovery, SCM
>            Reporter: Siddhant Sangwan
>            Assignee: Siddhant Sangwan
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.4.0
>
>
> {{ECUnderReplicationHandler}} checks if current replica datanodes + potential replica datanodes satisfy placement policy. If they don't, the targets are rejected and recovery fails. While this check makes some sense, it can block container recovery. Since under replication is more serious than mis replication, we should let a new replica be reconstructed even if it doesn't satisfy placement policy. 
> Also, we should rely on the policy to suggest a node that satisfies the policy - if there is none, the policy will fallback and try to suggest a node on a rack where the container is already present. 



--
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