[
https://issues.apache.org/jira/browse/HDDS-9737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephen O'Donnell resolved HDDS-9737.
-------------------------------------
Fix Version/s: 1.4.0
Resolution: Fixed
> Legacy Replication Manager should consider that UNHEALTHY replicas might be
> decommissioning
> -------------------------------------------------------------------------------------------
>
> Key: HDDS-9737
> URL: https://issues.apache.org/jira/browse/HDDS-9737
> 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
>
>
> The initial problem was that {{LegacyReplicationManager}} was not considering
> that UNHEALTHY replicas could be decommissioning or entering maintenance. So,
> its logic for determining whether a container with all UNHEALTHY replicas is
> under replicated was flawed. This was fixed in HDDS-9652. The fix simply used
> existing logic in {{RatisContainerReplicaCount}} that is able to account for
> decommissioning UNHEALTHY replicas. However this didn't completely fix the
> problem because {{DatanodeAdminMonitorImpl}} also needs to be updated.
> {{RatisContainerReplicaCount}} (extended by
> {{{}LegacyRatisContainerReplicaCount{}}}, exclusively used by the legacy
> replication manager) is the interface between the replication manager and the
> decommissioning flow. It's used by both to determine whether a container is
> under replicated. This Jira should make it so that when a container has all
> UNHEALTHY replicas, {{DatanodeAdminMonitor}} receives the
> {{LegacyRatisContainerReplicaCount}} object which can handle decommissioning
> UNHEALTHY containers.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
