[MAPREDUCE-3460] MR AM can hang if containers are allocated on a node blacklisted by the AM

• Type: Bug
• Status: Closed
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 0.23.0, 2.0.0-alpha
• Fix Version/s: 0.23.1
• Component/s: mr-am, mrv2
• Target Version/s: 0.23.1
• Assignee: Robert Joseph Evans
• Reporter: Siddharth Seth
• Created: 23/Nov/11 04:16
• Updated: 10/Mar/15 04:31
• Resolved: 02/Dec/11 22:23

Description

When an AM is assigned a FAILED_MAP (priority = 5) container on a nodemanager which it has blacklisted - it tries to
find a corresponding container request.
This uses the hostname to find the matching container request - and can end up returning any of the ContainerRequests which may have requested a container on this node. This container request is cleaned to remove the bad node - and then added back to the RM 'ask' list.
The AM cleans the 'ask' list after each heartbeat - The RM Allocator is still aware of the priority=5 container (in 'remoteRequestsTable') - but this never gets added back to the 'ask' set - which is what is sent to the RM.