hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tom White (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-252) Unmanaged AMs should not have to set the AM's ContainerLaunchContext
Date Tue, 18 Dec 2012 16:46:14 GMT

    [ https://issues.apache.org/jira/browse/YARN-252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13535034#comment-13535034
] 

Tom White commented on YARN-252:
--------------------------------

Bikas - it's a toy YARN app written in Java that runs the AM from the client. I agree we need
both.
                
> Unmanaged AMs should not have to set the AM's ContainerLaunchContext
> --------------------------------------------------------------------
>
>                 Key: YARN-252
>                 URL: https://issues.apache.org/jira/browse/YARN-252
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: applications
>    Affects Versions: 2.0.2-alpha
>            Reporter: Tom White
>            Assignee: Tom White
>         Attachments: YARN-252.patch, YARN-252.patch, YARN-252.patch
>
>
> Not calling ApplicationSubmissionContext#setAMContainerSpec causes a NPE, even though
the container is not used (since the AM doesn't run in a managed YARN container).

--
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

Mime
View raw message