Uploaded image for project: 'Apache Ozone'
  1. Apache Ozone
  2. HDDS-4656 Add a container balancer tool or service for HDDS
  3. HDDS-5760

ContainerBalancer incorrectly exits an iteration early without checking move results.

    XMLWordPrintableJSON

Details

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

    Description

      In ContainerBalancer#doIteration:

            IterationResult result = checkConditionsForBalancing();
            if (result != null) {
              LOG.info("Exiting current iteration: {}", result);
              return result;
            }
      

      Leads to the iteration ending early without checking move results and updating metrics. This bug can be reproduced by setting the maxSizeToMovePerIteration to a small value such as 5GB that allows one container move before ending the iteration.

      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: