[HADOOP-1158] JobTracker should collect statistics of failed map output fetches, and take decisions to reexecute map tasks and/or restart the (possibly faulty) Jetty server on the TaskTracker

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.12.2
• Fix Version/s: 0.15.0
• Assignee: Arun Murthy
• Reporter: Devaraj Das
• Created: 25/Mar/07 18:45
• Updated: 08/Jul/09 16:52
• Resolved: 23/Aug/07 16:36

Description

The JobTracker should keep a track (with feedback from Reducers) of how many times a fetch for a particular map output failed. If this exceeds a certain threshold, then that map should be declared as lost, and should be reexecuted elsewhere. Based on the number of such complaints from Reducers, the JobTracker can blacklist the TaskTracker. This will make the framework reliable - it will take care of (faulty) TaskTrackers that sometimes always fail to serve up map outputs (for which exceptions are not properly raised/handled, for e.g., if the exception/problem happens in the Jetty server).

Issue Links

• duplicates: HADOOP-1454 Reducer doesn't track failed fetches and gets stuck
• relates to: MAPREDUCE-79 Ignored IOExceptions from MapOutputLocation.java:getFile lead to hung reduces