[
https://issues.apache.org/jira/browse/MAPREDUCE-430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arun C Murthy updated MAPREDUCE-430:
------------------------------------
Status: Open (was: Patch Available)
I had a chat with Amar to explain my take on this:
# {Map|Reduce}Task shouldn't catch Throwable except for the parts where they
deal with threads e.g. copier threads or merge threads in which case they
should use a Throwable variable to save the error and check for it.
# Child should catch Throwable, inform the TaskTracker via
TaskUmbilicalProtocal.fatalError or such and then exit.
Thoughts?
> Task stuck in cleanup with OutOfMemoryErrors
> --------------------------------------------
>
> Key: MAPREDUCE-430
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-430
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Reporter: Amareshwari Sriramadasu
> Assignee: Amar Kamat
> Fix For: 0.20.1
>
> Attachments: MAPREDUCE-430-v1.6-branch-0.20.patch,
> MAPREDUCE-430-v1.6.patch, MAPREDUCE-430-v1.7.patch, MAPREDUCE-430-v1.8.patch
>
>
> Obesrved a task with OutOfMemory error, stuck in cleanup.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
