[MAPREDUCE-5982] Task attempts that fail from the ASSIGNED state can disappear

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.23.10, 2.2.1, 2.7.1
• Fix Version/s: 2.8.0, 2.7.2, 2.6.4, 3.0.0-alpha1
• Component/s: mr-am
• Target Version/s: 2.6.4
• Hadoop Flags: Reviewed
• Assignee: Chang Li
• Reporter: Jason Darrell Lowe
• Created: 18/Jul/14 16:14
• Updated: 06/Jan/17 07:30
• Resolved: 17/Sep/15 21:40

Description

If a task attempt fails in the ASSIGNED state, e.g.: container launch fails, then it can disappear from the job history. The task overview page will show subsequent attempts but the attempt in question is simply missing. For example attempt ID 1 appears but the attempt ID 0 is missing. Similarly in the job overview page the task attempt doesn't appear in any of the failed/killed/succeeded counts or pages. It's as if the task attempt never existed, but the AM logs show otherwise.

Issue Links

• breaks: MAPREDUCE-6492 AsyncDispatcher exit with NPE on TaskAttemptImpl#sendJHStartEventForAssignedFailTask
• is duplicated by: MAPREDUCE-4758 jobhistory web ui not showing correct # failed reducers