[
https://issues.apache.org/jira/browse/HDDS-9729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Attila Doroszlai updated HDDS-9729:
-----------------------------------
Fix Version/s: 1.4.0
> Provide API to check a container via Replication Manager
> --------------------------------------------------------
>
> Key: HDDS-9729
> URL: https://issues.apache.org/jira/browse/HDDS-9729
> Project: Apache Ozone
> Issue Type: Sub-task
> Components: SCM
> Reporter: Stephen O'Donnell
> Assignee: Stephen O'Donnell
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.4.0
>
>
> Replication Manager has increasingly complex logic used to check if a
> container is under or over replicated, unhealthy etc.
> Other parts of the system, such as Decommission and Recon also need to know
> if a set of containers are healthy or not, but they currently have their own
> logic to do this, which can result in a mis-match in health states between RM
> and Recon or decommission.
> This PR exposes the container check chain used by RM to check containers, and
> allows it to be called in a read-only way, avoiding any commands being sent.
> The results of the call populate a ReplicationManagerReport instance passed
> into the command, which allows the call to check the state of containers
> checked.
> In a later PR, we plan to integrate the Decommission Monitor with this API so
> it does not have any of its own logic to determine if a container is
> under-replicated or not.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
