[MAPREDUCE-5900] Container preemption interpreted as task failures and eventually job failures

• Type: Sub-task
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.4.1
• Fix Version/s: 2.5.0
• Component/s: applicationmaster, mr-am, mrv2
• Target Version/s: 2.4.1
• Hadoop Flags: Reviewed
• Assignee: Mayank Bansal
• Reporter: Mayank Bansal
• Created: 21/May/14 18:06
• Updated: 10/Mar/15 04:30
• Resolved: 03/Jul/14 01:48

Description

We have Added preemption exit code needs to be incorporated
MR needs to recognize the special exit code value of -102 and interpret it as a container being killed instead of a container failure.

Issue Links

• depends upon: MAPREDUCE-4951 Container preemption interpreted as task failure
• is related to: MAPREDUCE-5848 MapReduce counts forcibly preempted containers as FAILED