Uploaded image for project: 'Apache Ozone'
  1. Apache Ozone
  2. HDDS-8699 Further Replication Manager Improvements
  3. HDDS-9729

Provide API to check a container via Replication Manager

    XMLWordPrintableJSON

Details

    • Sub-task
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • 1.4.0
    • SCM

    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

          Activity

            People

              sodonnell Stephen O'Donnell
              sodonnell Stephen O'Donnell
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: