You are viewing a plain text version of this content. The canonical link for it is here.

Posted to yarn-issues@hadoop.apache.org by "Hitesh Shah (JIRA)" <ji...@apache.org> on 2013/04/10 00:00:18 UTC

[jira] [Moved] (YARN-560) If AM fails due to overrunning resource limits, error not visible through UI sometimes

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

Hitesh Shah moved MAPREDUCE-3949 to YARN-560:
---------------------------------------------

    Affects Version/s:     (was: 0.23.2)
                           (was: 0.24.0)
                       0.23.3
                       2.0.0-alpha
                  Key: YARN-560  (was: MAPREDUCE-3949)
              Project: Hadoop YARN  (was: Hadoop Map/Reduce)
    
> If AM fails due to overrunning resource limits, error not visible through UI sometimes
> --------------------------------------------------------------------------------------
>
>                 Key: YARN-560
>                 URL: https://issues.apache.org/jira/browse/YARN-560
>             Project: Hadoop YARN
>          Issue Type: Bug
>    Affects Versions: 2.0.0-alpha, 0.23.3
>            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