[MAPREDUCE-4984] AM leaves unwanted node/rack requests after container has been assigned

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 2.0.2-alpha
• Component/s: applicationmaster, mr-am
• Assignee: Sandy Ryza
• Reporter: Sandy Ryza
• Created: 06/Feb/13 23:03
• Updated: 06/Feb/13 23:59
• Resolved: 06/Feb/13 23:59

Description

Consider the following situation:
node1, node2, and node3 are all on rack1
task1 is submitted with resource requests on node1, node2, rack1, and *
task2 is submitted with resource requests on node3, rack1, and *

The RM gives a container to the app on node1, on which the AM assigns task1. While node1 is removed from the scheduler's bookkeeping, node2 is not, so its delay scheduling will try as hard to assign a container there is it would to node3.

The AM should cancel its request for node2 on its next heartbeat by sending a resource request with # containers = 0.

Issue Links

• duplicates: MAPREDUCE-4671 AM does not tell the RM about container requests that are no longer needed