[
https://issues.apache.org/jira/browse/HDDS-9902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephen O'Donnell resolved HDDS-9902.
-------------------------------------
Fix Version/s: 1.4.0
Resolution: Fixed
> Decommission: Admin monitor should call RM.checkContainerState to check for
> under-replication
> ---------------------------------------------------------------------------------------------
>
> Key: HDDS-9902
> URL: https://issues.apache.org/jira/browse/HDDS-9902
> Project: Apache Ozone
> Issue Type: Improvement
> Components: SCM
> Reporter: Stephen O'Donnell
> Assignee: Stephen O'Donnell
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.4.0
>
>
> The logic in ReplicationManager is increasingly complex due to various edge
> cases around unhealthy and quasi-closed containers, and the differences
> between EC and Ratis.
> It therefore makes sense for DatanodeAdminMonitor to call the new API
> replicationManager.checkContainerState and then check the report for
> under-replicated, rather than using the ReplicaCount objects.
> In making this change, I needed to make a change in the EC under-replication
> handling where the container is unhealthy / unrecoverable but also has
> decommissioning indexes, as it was not being reported as under-replicated
> previously.
> I also refactored the decommission monitor slightly to remove references to
> containers as "unhealthy" when they are really unclosed - renaming the
> metrics and variables to unClosed.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
