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

SchedulerUtils improve way normalizeRequest sets the resource capabilities

    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 2.0.3-alpha
    • Fix Version/s: 2.1.0-beta
    • Component/s: scheduler
    • Labels:
      None

      Description

      In YARN-370, we changed it from setting the capability to directly setting memory and cores:

      • ask.setCapability(normalized);
        + ask.getCapability().setMemory(normalized.getMemory());
        + ask.getCapability().setVirtualCores(normalized.getVirtualCores());

      We did this because it is directly setting the values in the original resource object passed in when the AM gets allocated and without it the AM doesn't get the resource normalized correctly in the submission context. See YARN-370 for more details.

      I think we should find a better way of doing this long term, one so we don't have to keep adding things there when new resources are added, two because its a bit confusing as to what its doing and prone to someone accidentally breaking it in the future again. Something closer to what Arun suggested in YARN-370 would be better but we need to make sure all the places work and get some more testing on it before putting it in.

        Attachments

        1. YARN-382_demo.patch
          95 kB
          Zhijie Shen
        2. YARN-382_2.patch
          9 kB
          Zhijie Shen
        3. YARN-382_1.patch
          9 kB
          Zhijie Shen

          Issue Links

            Activity

              People

              • Assignee:
                zjshen Zhijie Shen
                Reporter:
                tgraves Thomas Graves
              • Votes:
                0 Vote for this issue
                Watchers:
                10 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: