[YARN-407] The requested AM memory is not checked against the maximum resource capacity in ResourceMgrDelegate and MRAppMaster

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Duplicate
• Assignee: Zhijie Shen
• Reporter: Zhijie Shen
• Created: 15/Feb/13 22:36
• Updated: 19/Feb/13 19:16
• Resolved: 19/Feb/13 19:14

Description

For the MR jobs, the requested AM memory is at the risk of being larger than the maximum resource capacity. It is because the logic to check the requested AM memory against the maximum resource capacity is missing in ResourceMgrDelegate and MRAppMaster. In contrast, this logic exists in Client and ApplicationMaster of the distributed shell.

Another potential risk is that the requested AM memory is likely to be rounded up when being normalized, therefore the after-normalization AM memory can be larger than the maximum resource capacity as well.

Issue Links

• is duplicated by: YARN-193 Scheduler.normalizeRequest does not account for allocation requests that exceed maximumAllocation limits
• relates to: YARN-389 Infinitely assigning containers when the required resource exceeds the cluster's absolute capacity