[YARN-394] RM should be able to return requests that it cannot fulfill

• Type: Sub-task
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Assignee: Unassigned
• Reporter: Bikas Saha
• Created: 12/Feb/13 02:18
• Updated: 01/May/15 21:20

Description

Currently, the RM has no way of returning requests that cannot be met. e.g. if the app wants a specific node and that node dies, then the RM should return that request instead of holding onto to it indefinitely.

Some situations in which this would be useful are:

• After YARN-392, requests are location specific, and the locations that were requested are no longer in the cluster.
• A high memory machine is lost, and resource requests above certain sizes are no longer able to be satisfied anywhere.
• All nodes in the cluster become unavailable.

At these points, there is no way the RM can inform the apps about its inability to allocate requests.

Issue Links

• is related to: YARN-389 Infinitely assigning containers when the required resource exceeds the cluster's absolute capacity
• is related to: YARN-56 Handle container requests that request more resources than currently available in the cluster
• relates to: YARN-957 Capacity Scheduler tries to reserve the memory more than what node manager reports.
• relates to: YARN-1105 RM or YarnClient to notify AMs if resource requests cannot be satisfied