[YARN-2422] yarn.scheduler.maximum-allocation-mb should not be hard-coded in yarn-default.xml

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Won't Fix
• Affects Version/s: 2.6.0
• Component/s: scheduler
• Assignee: Gopal Vijayaraghavan
• Reporter: Gopal Vijayaraghavan
• Created: 15/Aug/14 22:11
• Updated: 18/Sep/14 01:58
• Resolved: 18/Sep/14 01:58

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.

Issue Links

• is related to: YARN-2555 Effective max-allocation-* should consider biggest node