[
https://issues.apache.org/jira/browse/MAPREDUCE-3949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13627082#comment-13627082
]
Ravi Prakash commented on MAPREDUCE-3949:
-----------------------------------------
The way to surely trigger the race is
1. Debug the NM and RM.
2. Set a breakpoint on these lines:
- ContainerLaunch.java:347 : new DelayedProcessKiller(user, processId,
sleepDelayBeforeSigKill, Signal.KILL, exec).start();
- RMContainerImpl.java:289 : RMContainerFinishedEvent finishedEvent =
(RMContainerFinishedEvent) event;
Run a job sure to exceed its container limits. Continue on both breakpoints
(its just to give enough time to the AM to unregister)
> If AM fails due to overrunning resource limits, error not visible through UI
> sometimes
> --------------------------------------------------------------------------------------
>
> Key: MAPREDUCE-3949
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3949
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Affects Versions: 0.24.0, 0.23.2
> Reporter: Todd Lipcon
> Assignee: Ravi Prakash
> Priority: Minor
> Attachments: MAPREDUCE-3949.patch
>
>
> I had a case where an MR AM eclipsed the configured memory limit. This caused
> the AM's container to get killed, but nowhere accessible through the web UI
> showed these diagnostics. I had to go view the NM's logs via ssh before I
> could figure out what had happened to my application.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira