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

Effective max-allocation-* should consider biggest node

    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Major
    • Resolution: Duplicate
    • Affects Version/s: 2.5.1
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • Target Version/s:

      Description

      The effective max-allocation-mb should be min(admin-configured-max-allocation-mb, max-mb-on-one-node), so we can reject container requests for resources larger than any node. Today, these requests wait forever.

      We should do this for all resources and update the effective value on node updates.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                kasha Karthik Kambatla
              • Votes:
                0 Vote for this issue
                Watchers:
                7 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: