[YARN-389] Infinitely assigning containers when the required resource exceeds the cluster's absolute capacity

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Target Version/s: 2.1.1-beta
• Assignee: Omkar Vinit Joshi
• Reporter: Zhijie Shen
• Created: 08/Feb/13 08:36
• Updated: 02/Sep/13 01:44

Description

I've run wordcount example on branch-2 and trunk. I've set yarn.nodemanager.resource.memory-mb to 1G and yarn.app.mapreduce.am.resource.mb to 1.5G. Therefore, resourcemanager is to assign a 2G AM container for AM. However, the nodemanager doesn't have enough memory to assign the container. The problem is that the assignment operation will be repeated infinitely, if the assignment cannot be accomplished. Logs follow.

Issue Links

• is related to: YARN-407 The requested AM memory is not checked against the maximum resource capacity in ResourceMgrDelegate and MRAppMaster
• is related to: YARN-56 Handle container requests that request more resources than currently available in the cluster
• relates to: YARN-394 RM should be able to return requests that it cannot fulfill
• relates to: YARN-957 Capacity Scheduler tries to reserve the memory more than what node manager reports.