Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
0.20.2, 0.20.205.0
-
None
-
None
-
I just committed this. Thanks Anupam!
Description
During the execution of a large job, the map tasks timeout:
INFO mapred.JobClient: Task Id : attempt_201010290414_60974_m_000057_1, Status : FAILED
Task attempt_201010290414_60974_m_000057_1 failed to report status for 609 seconds. Killing!
The bug is in the fact that the mapper has already finished, and, according to the logs, the timeout occurs during the merge sort phase.
The intermediate data generated by the map task is quite large. So I think this is the problem.
The logs show that the merge-sort was running for 10 minutes when the task was killed.
I think the mapred.Merger should call Reporter.progress() somewhere.
Attachments
Attachments
Issue Links
- relates to
-
MAPREDUCE-2177 The wait for spill completion should call Condition.awaitNanos(long nanosTimeout)
- Open