Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
2.0.0-alpha
-
None
Description
What happens is that the number of reducers ramp up until they occupy all of the job's containers, at which point the maps no longer make any progress and the job hangs.
When the same job is run with the CapacityScheduler it succeeds, so this looks like a FifoScheduler bug.
Attachments
Attachments
Issue Links
- is duplicated by
-
MAPREDUCE-4358 Reducers are assigned containers before all maps are assigned containers
- Resolved
-
MAPREDUCE-4613 Scheduling of reduce tasks results in starvation
- Resolved
- is related to
-
MAPREDUCE-4560 Job can get stuck in a deadlock between mappers and reducers for low values of mapreduce.job.reduce.slowstart.completedmaps (<<1)
- Resolved