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

Changes in scheduler to identify resource-requests explicitly by allocation-id

    XMLWordPrintableJSON

Details

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

    Description

      YARN-4879 puts forward the notion of identifying allocate requests explicitly. This JIRA is to track the changes in RM app scheduling data structures to accomplish it. Please refer to the design doc in the parent JIRA for details.

      Attachments

        1. YARN-4888.001.patch
          235 kB
          Arun Suresh
        2. YARN-4888-v0.patch
          34 kB
          Subramaniam Krishnan
        3. YARN-4888-v2.patch
          49 kB
          Subramaniam Krishnan
        4. YARN-4888-v3.patch
          49 kB
          Subramaniam Krishnan
        5. YARN-4888-v4.patch
          55 kB
          Subramaniam Krishnan
        6. YARN-4888-v5.patch
          51 kB
          Subramaniam Krishnan
        7. YARN-4888-v6.patch
          50 kB
          Subramaniam Krishnan
        8. YARN-4888-v7.patch
          33 kB
          Subramaniam Krishnan
        9. YARN-4888-v8.patch
          33 kB
          Subramaniam Krishnan
        10. YARN-4888-WIP.patch
          232 kB
          Subramaniam Krishnan

        Issue Links

          causes

          Bug - A problem which impairs or prevents the functions of the product. YARN-7466 ResourceRequest has a different default for allocationRequestId than Container

          • Major - Major loss of function.
          • Resolved
          depends upon

          Sub-task - The sub-task of the issue YARN-4887 AM-RM protocol changes for identifying resource-requests explicitly

          • Major - Major loss of function.
          • Resolved
          is blocked by

          Sub-task - The sub-task of the issue YARN-5392 Replace use of Priority in the Scheduling infrastructure with an opaque ShedulerRequestKey

          • Major - Major loss of function.
          • Resolved
          is depended upon by

          Sub-task - The sub-task of the issue YARN-4889 Changes in AMRMClient for identifying resource-requests explicitly

          • Major - Major loss of function.
          • Resolved

          Improvement - An improvement or enhancement to an existing feature or task. YARN-5225 Move to a simple clean AMRMClientImpl (v2)

          • Major - Major loss of function.
          • Open

          Activity

            People

              subru Subramaniam Krishnan
              subru Subramaniam Krishnan
              Votes:
              0 Vote for this issue
              Watchers:
              11 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: