[jira] [Updated] (HDDS-9354) LegacyReplicationManager: Unhealthy replicas of a sufficiently replicated container can block decommissioning

["Attila Doroszlai (Jira)" <ji...@apache.org>]

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

Attila Doroszlai updated HDDS-9354:
-----------------------------------
    Fix Version/s: 1.4.0

> LegacyReplicationManager: Unhealthy replicas of a sufficiently replicated container can block decommissioning
> -------------------------------------------------------------------------------------------------------------
>
>                 Key: HDDS-9354
>                 URL: https://issues.apache.org/jira/browse/HDDS-9354
>             Project: Apache Ozone
>          Issue Type: Sub-task
>          Components: SCM
>            Reporter: Siddhant Sangwan
>            Assignee: Siddhant Sangwan
>            Priority: Critical
>              Labels: pull-request-available
>             Fix For: 1.4.0
>
>
> Mix of quasi-closed and unhealthy replicas blocks decommission even if sufficiently replicated.
> a. Caused when only some of the replicas hit the error during write.
> b. Can be fixed by removing this check:
> {code}
> if (!replicaSet.isHealthy()) {
>           if (LOG.isDebugEnabled()) {
>             unhealthyIDs.add(cid);
>           }
>           if (unhealthy < CONTAINER_DETAILS_LOGGING_LIMIT
> {code}
> However, simply removing that check is not a complete solution. We need to try and preserve any UNHEALTHY replicas that have the greatest Sequence ID. https://issues.apache.org/jira/browse/HDDS-9321 takes care of the Legacy Replication Manager side of things to preserve such UNHEALTHY replicas. This jira focuses on the Decommissioning side.



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