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

Scheduler should consider max-allocation-* in conjunction with the largest node

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 2.5.1
    • 2.7.0
    • scheduler
    • None
    • Reviewed

    Description

      If the scheduler max-allocation-* values are larger than the resources available on the largest node in the cluster, an application requesting resources between the two values will be accepted by the scheduler but the requests will never be satisfied. The app essentially hangs forever.

      Attachments

        1. YARN-2604.patch
          14 kB
          Robert Kanter
        2. YARN-2604.patch
          18 kB
          Robert Kanter
        3. YARN-2604.patch
          19 kB
          Robert Kanter
        4. YARN-2604.patch
          32 kB
          Robert Kanter
        5. YARN-2604.patch
          32 kB
          Robert Kanter
        6. YARN-2604.patch
          30 kB
          Robert Kanter

        Issue Links

          breaks

          Bug - A problem which impairs or prevents the functions of the product. YARN-3027 Scheduler should use totalAvailable resource from node instead of availableResource for maxAllocation

          • Major - Major loss of function.
          • Closed
          duplicates

          Improvement - An improvement or enhancement to an existing feature or task. YARN-56 Handle container requests that request more resources than currently available in the cluster

          • Major - Major loss of function.
          • Open

          Activity

            People

              rkanter Robert Kanter
              kasha Karthik Kambatla
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: