[MAPREDUCE-5060] Fetch failures that time out only count against the first map task

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Fix Version/s: 0.23.7, 2.1.0-beta
• Target Version/s: 0.23.7
• Hadoop Flags: Reviewed
• Assignee: Robert Joseph Evans
• Reporter: Robert Joseph Evans
• Created: 12/Mar/13 19:44
• Updated: 27/Aug/13 22:22
• Resolved: 12/Mar/13 23:00

Description

When a fetch failure happens, if the socket has already "connected" it is only counted against the first map task. But most of the time it is because of an issue with the Node itself, not the individual map task, and as such all failures when trying to initiate the connection should count against all of the tasks.

This caused a particularly unfortunate job to take an hour an a half longer then it needed to.