Uploaded image for project: 'Hadoop YARN'
  1. Hadoop YARN
  2. YARN-7069 [Umbrella] YARN Resource Profiles phase#2 enhancements
  3. YARN-7292

Retrospect Resource Profile Behavior for overriding capability



    • Sub-task
    • Status: Resolved
    • Blocker
    • Resolution: Fixed
    • None
    • 3.1.0
    • None
    • Reviewed


      Had discussions with templedf, vvasudev, sunilg offline. There're a couple of resource profile related behaviors might need to be updated:

      1) Configure resource profile in server side or client side:

      Currently resource profile can be only configured centrally:

      • Advantages:
        A given resource profile has a the same meaning in the cluster. It won’t change when we run different apps in different configurations. A job can run under Amazon’s G2.8X can also run on YARN with G2.8X profile. A side benefit is YARN scheduler can potentially do better bin packing.
      • Disadvantages:
        Hard for applications to add their own resource profiles.

      2) Do we really need mandatory resource profiles such as minimum/maximum/default?

      3) Should we send resource profile name inside ResourceRequest, or should client/AM translate it to resource and set it to the existing resource fields?

      4) Related to above, should we allow resource overrides or client/AM should send final resource to RM?


        1. YARN-7292.wip.001.patch
          52 kB
          Wangda Tan
        2. YARN-7292.007.patch
          105 kB
          Wangda Tan
        3. YARN-7292.006.patch
          104 kB
          Wangda Tan
        4. YARN-7292.005.patch
          98 kB
          Wangda Tan
        5. YARN-7292.004.patch
          100 kB
          Sunil G
        6. YARN-7292.003.patch
          96 kB
          Wangda Tan
        7. YARN-7292.002.patch
          96 kB
          Wangda Tan



            leftnoteasy Wangda Tan
            leftnoteasy Wangda Tan
            0 Vote for this issue
            5 Start watching this issue