[jira] [Updated] (HDDS-9652) Legacy RM will not replicate all unhealthy containers when some are decommissioning

["ASF GitHub Bot (Jira)" <ji...@apache.org>]

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

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

> Legacy RM will not replicate all unhealthy containers when some are decommissioning
> -----------------------------------------------------------------------------------
>
>                 Key: HDDS-9652
>                 URL: https://issues.apache.org/jira/browse/HDDS-9652
>             Project: Apache Ozone
>          Issue Type: Improvement
>          Components: Ozone Datanode, SCM
>            Reporter: Stephen O'Donnell
>            Assignee: Stephen O'Donnell
>            Priority: Major
>              Labels: pull-request-available
>
> In a situation where a container is closed or quasi-closed with all unhealthy replicas, the legacy Replication Manager will not replicate the unhealthy containers if the under replication is caused by decommission.
> Ie, if we have 3 replicas:
> IN_SERVICE, unhealthy
> IN_SERVICE, unhealthy
> DECOMMISSIOING, unhealthy
> Then the legacy RM will take no action and decommission will be stuck.
> The new RM handles this state correctly and does not need to be changed.
> Additionally, in KeyValueContainer.java, unhealthy replicas cannot be exported / replicated, so even if the RM was not present, replication still could not happen.
> This change corrects both issues and adds a couple of extra tests to the new RM to prove it works ok.



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