Details
-
Bug
-
Status: Closed
-
Blocker
-
Resolution: Fixed
-
None
-
None
-
None
Description
Sometimes when a map task is lost while the map-output fetch is happening from the TT for that task, and the lost map has successfully executed on some other node, the event for that successful execution is lost at the fetching TT. The fetching TT might eventually fail to fetch the output for the lost task, but then since the event for the new run of the lost map might also have been lost, the fetching TT might hang.
This "hung" problem was discovered while working on HADOOP-1060.
Attachments
Attachments
Issue Links
- blocks
-
HADOOP-1060 IndexOutOfBoundsException in JobInProgress.updateTaskStatus leads to hung jobs
- Closed