You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-dev@hadoop.apache.org by "Todd Lipcon (Created) (JIRA)" <ji...@apache.org> on 2012/03/01 02:21:57 UTC
[jira] [Created] (MAPREDUCE-3949) If AM fails due to overrunning
resource limits, error not visible through UI
If AM fails due to overrunning resource limits, error not visible through UI
----------------------------------------------------------------------------
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
Priority: Minor
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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (MAPREDUCE-3949) If AM fails due to overrunning
resource limits, error not visible through UI
Posted by "Vinod Kumar Vavilapalli (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vinod Kumar Vavilapalli resolved MAPREDUCE-3949.
------------------------------------------------
Resolution: Duplicate
> If AM fails due to overrunning resource limits, error not visible through UI
> ----------------------------------------------------------------------------
>
> 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
> Priority: Minor
>
> 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira