Uploaded image for project: 'Hadoop YARN'
  1. Hadoop YARN
  2. YARN-8917

Absolute (maximum) capacity of level3+ queues is wrongly calculated for absolute resource

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Critical
    • Resolution: Fixed
    • Affects Version/s: 3.2.1
    • Fix Version/s: 3.3.0, 3.2.1
    • Component/s: capacityscheduler
    • Labels:
      None
    • Target Version/s:
    • Hadoop Flags:
      Reviewed

      Description

      Absolute capacity should be equal to multiply capacity by parent-queue's absolute-capacity,
      but currently it's calculated as dividing capacity by parent-queue's absolute-capacity.
      Calculation for absolute-maximum-capacity has the same problem.

      For example: 
      root.a   capacity=0.4   maximum-capacity=0.8
      root.a.a1   capacity=0.5  maximum-capacity=0.6
      Absolute capacity of root.a.a1 should be 0.2 but is wrongly calculated as 1.25
      Absolute maximum capacity of root.a.a1 should be 0.48 but is wrongly calculated as 0.75

      Moreover:
      childQueue.getQueueCapacities().getCapacity()  should be changed to childQueue.getQueueCapacities().getCapacity(label) to avoid getting wrong capacity from default partition when calculating for a non-default partition.

        Attachments

        1. YARN-8917.001.patch
          9 kB
          Tao Yang
        2. YARN-8917.002.patch
          10 kB
          Tao Yang

          Issue Links

            Activity

              People

              • Assignee:
                Tao Yang Tao Yang
                Reporter:
                Tao Yang Tao Yang
              • Votes:
                0 Vote for this issue
                Watchers:
                9 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: