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

yarn.scheduler.maximum-allocation-mb should not be hard-coded in yarn-default.xml

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Minor
    • Resolution: Won't Fix
    • Affects Version/s: 2.6.0
    • Fix Version/s: None
    • Component/s: scheduler
    • Labels:
      None

      Description

      Cluster with 40Gb NM refuses to run containers >8Gb.

      It was finally tracked down to yarn-default.xml hard-coding it to 8Gb.

      In case of lack of a better override, it should default to - ${yarn.nodemanager.resource.memory-mb} instead of a hard-coded 8Gb.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                gopalv Gopal V
                Reporter:
                gopalv Gopal V
              • Votes:
                0 Vote for this issue
                Watchers:
                7 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: