[ 
https://issues.apache.org/jira/browse/MAPREDUCE-430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Amar Kamat updated MAPREDUCE-430:
---------------------------------

    Release Note: Various code paths in the framework caught Throwable and 
tried to do inline cleanup. In case of OOM errors, such inline-cleanups can 
result into hung jvms. With this fix, the TaskTracker provides a api to report 
fatal errors (any throwable other than FSErrror and Exceptions). On catching a 
Throwable, Mapper/Reducer tries to inform the TT. 

> 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: MAPRED-430-v1.13-example.patch, 
> MAPREDUCE-430-v1.11.patch, MAPREDUCE-430-v1.12-branch-0.20.patch, 
> MAPREDUCE-430-v1.12.patch, MAPREDUCE-430-v1.13-branch-0.20.patch, 
> MAPREDUCE-430-v1.13.patch, 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.

Reply via email to