[
https://issues.apache.org/jira/browse/MAPREDUCE-430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12747334#action_12747334
]
Devaraj Das commented on MAPREDUCE-430:
---------------------------------------
I'd be happier with the previous approach for 0.20. I believe it doesn't break
the existing behavior (I will look at the last patch in more detail today).
This seems like a good first step towards a probably better fix for the issue
as is proposed in the last comment. The last proposal seems like a much bigger
change and I propose that we thrash that design/implementation out as part of
0.21. 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.11.patch,
> MAPREDUCE-430-v1.12-branch-0.20.patch, MAPREDUCE-430-v1.12.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.
