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

Intraqueue preemption doesn't work across partitions

    XMLWordPrintableJSON

    Details

      Description

      Cluster:

      1 Node with label "A"

      yarn.scheduler.capacity.root.accessible-node-labels=*

      yarn.resourcemanager.monitor.capacity.preemption.intra-queue-preemption.enabled=true

      yarn.scheduler.capacity.root.default.minimum-user-limit-percent=50

       

      User 1:  Submit job Y require 10x cluster resources to queue, default, using label ""

      User 2: (after job Y starts) submit job Z to queue, default using label ""

       

      What we see: Job Z doesn't start until job Y releases resources. This happens because the pending requests for job Y and Z are in partition "". However, queue default is using resources in partition "A". Pending requests in partition "" don't cause intra queue preemptions in partition "A".

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              pjoneswork Paul Jones
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated: