Details
-
Bug
-
Status: Closed
-
Critical
-
Resolution: Fixed
-
0.11.2
-
None
-
None
Description
I ran a unit test (TestMRClassPath) that had a problem (likely in task initialization) that cause one of the maps to get "lost". The job tracker had the task as "assigned" but the task tracker did not know about it. It did not time out even after 30+ minutes.
Attachments
Attachments
Issue Links
- is related to
-
MAPREDUCE-167 SAXParseException causes test to run forever
- Resolved