[
https://issues.apache.org/jira/browse/MAPREDUCE-430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12745820#action_12745820
]
Arun C Murthy commented on MAPREDUCE-430:
-----------------------------------------
I'm thinking we can do:
{noformat}
try {
// existing stuff
} catch (FSError e) {
// ...
} catch (Throwable t) {
umblical.fatalError();
}
{noformat}
Thus we can allow the Child to exit if it can't do umbilical.fatalError(). I'm
thinking that we'll just do a best-effort to call {umbilical.fatalError}, I
don't think the jvm will get 'stuck' there. 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.
