The job hangs forever when some maps are failing.
1. Submit a MR job (feature start)
2. Some of the mappers failed (job fail)
Yes (We can control that some of the mappers always fail)
3 (2 for mapper tasks and 1 for reducer task)
The map-reduce job hangs when there’re some mappers fail.
MR will not correctly calculate the progress when there’re mappers fail in the job. So the user will never see the job completed in the progress report.
When a map task fails, it will not be counted in the progress calculating.
Let the progress be calculated as 1f when the task ends with status FAILED or KILLED.