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

CapacityScheduler should respect maximum node resource when per-queue maximum-allocation is being used.

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.10.0, 3.2.0, 2.9.2, 3.0.4, 3.1.2, 3.3.0, 2.8.6
    • Component/s: None
    • Labels:
      None

      Description

      This issue happens after YARN-8720.

      Before that, AMS uses scheduler.getMaximumAllocation to do the normalization. After that, AMS uses LeafQueue.getMaximumAllocation. The scheduler one uses nodeTracker.getMaximumAllocation, but the LeafQueue.getMaximum doesn't. 

      We should use the scheduler.getMaximumAllocation to cap the per-queue's maximum-allocation every time.

        Attachments

        1. YARN-8858.001.patch
          10 kB
          Wangda Tan
        2. YARN-8858.002.patch
          8 kB
          Wangda Tan
        3. YARN-8858-branch-2.8.001.patch
          6 kB
          Weiwei Yang
        4. YARN-8858-branch-2.8.002.patch
          7 kB
          Weiwei Yang

          Issue Links

            Activity

              People

              • Assignee:
                leftnoteasy Wangda Tan
                Reporter:
                ssathish@hortonworks.com Sumana Sathish
              • Votes:
                0 Vote for this issue
                Watchers:
                8 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: