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

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Minor
    • Resolution: Won't Fix
    • 2.6.0
    • None
    • scheduler
    • 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

        1. YARN-2422.1.patch
          0.7 kB
          Gopal Vijayaraghavan

        Issue Links

          is related to

          Improvement - An improvement or enhancement to an existing feature or task. YARN-2555 Effective max-allocation-* should consider biggest node

          • Major - Major loss of function.
          • Resolved

          Activity

            People

              gopalv Gopal Vijayaraghavan
              gopalv Gopal Vijayaraghavan
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: