Uploaded image for project: 'Apache Ozone'
  1. Apache Ozone
  2. HDDS-8350 Balancer Improvements
  3. HDDS-7218

balancer handling exception case for move immediate failure and failure later is different

    XMLWordPrintableJSON

Details

    • Sub-task
    • Status: Open
    • Minor
    • Resolution: Unresolved
    • None
    • None
    • None
    • None

    Description

      There is a difference in behaviour for handling exception in move.

      1. Exception occurred immediately, its logged and metrics ignored. (ContainerBalancer.moveContainer)
      2. If Exception occurred later in future for any one, all are treated as exception case and logged accordingly. Success cases are also treated as failure. (ContainerBalancer.checkIterationMoveResults)

      Both should have uniform behaviour.

      Attachments

        Activity

          People

            Unassigned Unassigned
            sumitagrawl Sumit Agrawal
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated: