[MAPREDUCE-4749] Killing multiple attempts of a task taker longer as more attempts are killed

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.1.0
• Fix Version/s: 1.1.1
• Hadoop Flags: Reviewed
• Assignee: Arpit Gupta
• Reporter: Arpit Gupta
• Created: 25/Oct/12 00:41
• Updated: 03/Dec/12 07:33
• Resolved: 10/Nov/12 02:37

Description

The following was noticed on a mr job running on hadoop 1.1.0

1. Start an mr job with 1 mapper

2. Wait for a min

3. Kill the first attempt of the mapper and then subsequently kill the other 3 attempts in order to fail the job

The time taken to kill the task grew exponentially.

1st attempt was killed immediately.
2nd attempt took a little over a min
3rd attempt took approx. 20 mins
4th attempt took around 3 hrs.

The command used to kill the attempt was "hadoop job -fail-task"

Note that the command returned immediately as soon as the fail attempt was accepted but the time the attempt was actually killed was as stated above.

Issue Links

• is broken by: MAPREDUCE-4088 Task stuck in JobLocalizer prevented other tasks on the same node from committing