hadoop-yarn-issues mailing list archives

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

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

Bikas Saha commented on YARN-252:

Patch looks good to me.

Thats interesting. My initial implementation of the client was to launch the AM in the same
JVM but then I decided against that because I thought one would want to run the AM just as
it was running in the cluster - ie. in its own process/JVM. It would be great to be able to
do both because that would solve other scenarios like yours. Would you mind sharing your use
case that did not fit the current implementation?

> 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

View raw message