Details
-
Sub-task
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
Description
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.
Attachments
Issue Links
- fixes
-
HDDS-9808 Decommission should get the correct ContainerReplicaCount object
- Resolved
- links to