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 "Tom White (JIRA)" <ji...@apache.org> on 2012/12/03 13:57:58 UTC

[jira] [Updated] (YARN-252) Unmanaged AMs should not have to set the ContainerLaunchContext

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

Tom White updated YARN-252:
---------------------------

    Attachment: YARN-252.patch

Bikas, thanks for taking a look. I was thinking that since there is no AM container in an unmanaged situation then setting one doesn't make sense - and in fact requiring that one be set is very confusing for YARN application writers. For YARN-255 the tokens could be passed by another API call.

I've updated the patch to assert the context is null for unmanaged AMs.
                
> Unmanaged AMs should not have to set the 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
>
>
> 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