hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Devaraj Das (JIRA)" <j...@apache.org>
Subject [jira] Commented: (MAPREDUCE-430) Task stuck in cleanup with OutOfMemoryErrors
Date Fri, 21 Aug 2009 05:58:14 GMT

    [ https://issues.apache.org/jira/browse/MAPREDUCE-430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12745817#action_12745817
] 

Devaraj Das commented on MAPREDUCE-430:
---------------------------------------

I am worried that the communication to the TT might get stuck if it was a OOM. On the other
hand, System.exit has a much better probability of making the process exit. So my thinking
for Child.java is:

try {
 // do the existing stuff 
} catch (OutOfMemoryError) {
  System.exit(-1);

} catch (FSError fse) {
 // do the existing stuff
} catch (Throwable t ) {
// do the existing stuff
} finally {
// do the existing stuff
}

> 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.


Mime
View raw message