[
https://issues.apache.org/jira/browse/MAPREDUCE-430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12733537#action_12733537
]
Amareshwari Sriramadasu commented on MAPREDUCE-430:
---------------------------------------------------
bq. Did the task which threw up OOMError eventually time-out and was it
declared as 'FAILED' ?
No. The task alive and stuck. I think pingThread was sending updates without
any problem.
bq. I'm worried we have other bugs in the framework such as assigning the
cleanup task to a jvm which is already dead and so on.
This would never happen, because task assignment happens when jvm comes back
asking for a task using TaskUmbilicalProtocol.getTask
> 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
>
>
> 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.
