Details

    • Sub-task
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • 2.8.0, 3.0.0-alpha1
    • capacityscheduler
    • None
    • Reviewed

    Description

      In existing CapacityScheduler, when computing headroom of an application, it will only consider "non-labeled" nodes of this application.

      But it is possible the application is asking for labeled resources, so headroom-by-label (like 5G resource available under node-label=red) is required to get better resource allocation and avoid deadlocks such as MAPREDUCE-5928.

      This JIRA could involve both API changes (such as adding a label-to-available-resource map in AllocateResponse) and also internal changes in CapacityScheduler.

      Attachments

        1. YARN-3215.v1.001.patch
          13 kB
          Naganarasimha G R
        2. YARN-3215.v2.001.patch
          36 kB
          Naganarasimha G R
        3. YARN-3215.v2.002.patch
          38 kB
          Naganarasimha G R
        4. YARN-3215.v2.003.patch
          39 kB
          Naganarasimha G R
        5. YARN-3215.v2.branch-2.8.patch
          44 kB
          Wangda Tan
        6. YARN-3215.branch-2.8.v2.002.patch
          44 kB
          Naganarasimha G R

        Activity

          People

            Naganarasimha Naganarasimha G R
            leftnoteasy Wangda Tan
            Votes:
            0 Vote for this issue
            Watchers:
            14 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: