Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
-
None
Description
Noticed that the Map task's "last" progress message sometimes goes through even after the fix for HADOOP-1191. In reality, this could happen since we don't check for thread.isInterrupted() at each step in the path of the client RPC call. So the situation described in HADOOP-1191 remains. The effect of this is that the TaskTracker finally kills the task for not sending progress report for the configured number of seconds (if the process happens to be alive then).
Attachments
Attachments
Issue Links
- is related to
-
HADOOP-1191 MapTask should wait for the status reporting thread to die before invoking the TaskUmbilicalProtocol.done(taskid)
- Closed