Uploaded image for project: 'Apache Ozone'
  1. Apache Ozone
  2. HDDS-7759 Improve Ozone Replication Manager
  3. HDDS-8034

Check container replication health before scheduling move in MoveManager

    XMLWordPrintableJSON

Details

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

    Description

      MoveManager#move already checks if a container has any in-flight (pending) Adds or Deletes before scheduling a move. However, there is some time between the replication thread checking the health of a container and the UnhealthyReplicationProcessor thread scheduling Adds and Deletes. To be safe, we should also check the container's health in MoveManager before scheduling move.

      Attachments

        Issue Links

          Activity

            People

              siddhant Siddhant Sangwan
              siddhant Siddhant Sangwan
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: