[MAPREDUCE-4817] Hardcoded task ping timeout kills tasks localizing large amounts of data

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 0.23.3, 2.0.3-alpha
• Fix Version/s: 2.0.3-alpha, 0.23.6
• Component/s: applicationmaster, mr-am
• Target Version/s: 2.0.3-alpha, 0.23.6
• Assignee: Thomas Graves
• Reporter: Jason Darrell Lowe
• Created: 22/Nov/12 01:55
• Updated: 03/Sep/14 23:25
• Resolved: 28/Nov/12 19:25

Description

When a task is launched and spends more than 5 minutes localizing files, the AM will kill the task due to ping timeout. The AM's TaskHeartbeatHandler currently tracks tasks via a progress timeout and a ping timeout. The progress timeout can be controlled via mapreduce.task.timeout and even disabled by setting the property to 0. The ping timeout, however, is hardcoded to 5 minutes and cannot be configured. Therefore if the task takes too long localizing, it never gets running in order to ping back to the AM and the AM kills it due to ping timeout.