[MAPREDUCE-4228] mapreduce.job.reduce.slowstart.completedmaps is not working properly to delay the scheduling of the reduce tasks

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.23.1
• Fix Version/s: 0.23.3, 2.0.2-alpha
• Component/s: applicationmaster, mrv2
• Target Version/s: 0.23.3
• Assignee: Jason Darrell Lowe
• Reporter: Jason Darrell Lowe
• Created: 04/May/12 21:25
• Updated: 11/Oct/12 17:48
• Resolved: 26/Jun/12 19:25

Description

If no more map tasks need to be scheduled but not all have completed, the ApplicationMaster will start scheduling reducers even if the number of completed maps has not met the mapreduce.job.reduce.slowstart.completedmaps threshold. For example, if the property is set to 1.0 all maps should complete before any reducers are scheduled. However the reducers are scheduled as soon as the last map task is assigned to a container. For a job with very long-running maps, a cluster with enough capacity to launch all map tasks could cause reducers to launch prematurely and waste cluster resources.

Thanks to Phil Su for discovering this issue.