Uploaded image for project: 'Hadoop YARN'
  1. Hadoop YARN
  2. YARN-4879 Enhance Allocate Protocol to Identify Requests Explicitly
  3. YARN-5392

Replace use of Priority in the Scheduling infrastructure with an opaque ShedulerRequestKey

    XMLWordPrintableJSON

Details

    • Sub-task
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • 2.9.0, 3.0.0-alpha1
    • None
    • None

    Description

      Based on discussions in YARN-4888, this jira proposes to replace the use of Priority in the Scheduler infrastructure (Scheduler, Queues, SchedulerApp / Node etc.) with a more opaque and extensible SchedulerKey.

      Note: Even though SchedulerKey will be used by the internal scheduling infrastructure, It will not be exposed to the Client or the AM. The SchdulerKey is meant to be an internal construct that is derived from attributes of the ResourceRequest / ApplicationSubmissionContext / Scheduler Configuration etc.

      Attachments

        1. YARN-5392.001.patch
          245 kB
          Arun Suresh
        2. YARN-5392.002.patch
          278 kB
          Arun Suresh
        3. YARN-5392.003.patch
          285 kB
          Arun Suresh
        4. YARN-5392.004.patch
          254 kB
          Arun Suresh
        5. YARN-5392.005.patch
          225 kB
          Arun Suresh
        6. YARN-5392.006.patch
          209 kB
          Arun Suresh
        7. YARN-5392.007.patch
          210 kB
          Arun Suresh
        8. YARN-5392.008.patch
          214 kB
          Arun Suresh
        9. YARN-5392.009.patch
          212 kB
          Arun Suresh
        10. YARN-5392.010.patch
          212 kB
          Arun Suresh

        Issue Links

          Activity

            People

              asuresh Arun Suresh
              asuresh Arun Suresh
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: