[MAPREDUCE-3312] Make MR AM not send a stopContainer w/o corresponding start container

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.23.0, 2.0.0-alpha
• Fix Version/s: 0.23.1
• Component/s: mrv2
• Target Version/s: 0.23.0
• Hadoop Flags: Reviewed
• Release Note: Modified MR AM to not send a stop-container request for a container that isn't launched at all.
• Assignee: Robert Joseph Evans
• Reporter: Robert Joseph Evans
• Created: 30/Oct/11 00:21
• Updated: 10/Mar/15 04:32
• Resolved: 10/Jan/12 02:17

Description

This is a follow on to MAPREDUCE-3274. It is possible, although rare, for the MR AM to send a stop container before it sends a start container. This needs to stop that from happening. If a stop is found first it should prevent the start from being sent. It tries to do this, but only if the stop is currently pending.

Issue Links

• duplicates: MAPREDUCE-3622 findbug error during test-patch: org.apache.hadoop.mapreduce.v2.app.launcher.ContainerRemoteLaunchEvent defines equals but not hashCode