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 2022/10/19 20:27:00 UTC

[jira] [Assigned] (HDDS-7101) EC: ReplicationManager - handle UNHEALTHY replicas

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

Attila Doroszlai reassigned HDDS-7101:
--------------------------------------

    Assignee: Siddhant Sangwan  (was: Attila Doroszlai)

> EC: ReplicationManager - handle UNHEALTHY replicas
> --------------------------------------------------
>
>                 Key: HDDS-7101
>                 URL: https://issues.apache.org/jira/browse/HDDS-7101
>             Project: Apache Ozone
>          Issue Type: Sub-task
>            Reporter: Stephen O'Donnell
>            Assignee: Siddhant Sangwan
>            Priority: Major
>
> If the DN scrubber marks a container as UNHEALTHY, the EC Replication Manager logic needs to be able to deal with it. It needs to remove the unhealthy one, and create a new copy using EC Reconstruction.
> However we need to be careful to perhaps create the new replica before removing the unhealthy one. Also, if there are too many unhealthy, it would make the container unrecoverable, as there are not enough healthy replicas to try.
> The LegacyReplicationManager handles this in the handleUnstableContainer method, but I wonder if we would be better handling it in the underReplicationHandler, as it is basically a form of under replication.
> The logic to deal with it, is also going to be different from EC and Ratis.



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