hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alejandro Abdelnur (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-937) Fix unmanaged AM in non-secure/secure setup post YARN-701
Date Tue, 23 Jul 2013 13:12:49 GMT

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

Alejandro Abdelnur commented on YARN-937:

[~bikassaha], in the way I've using unmanaged AM I have a running service that hosts the AM
without forking a process. IMO, this is the powerful thing about unmanaged AMs. If I would
be to fork a new process to run the AM, why would I just use a managed AM.

[~daryn], the AM launcher, after creating an APP, forks a process to register it to the schedulers,
the new process does not have the launch context thus we need the token file in this case.
> Fix unmanaged AM in non-secure/secure setup post YARN-701
> ---------------------------------------------------------
>                 Key: YARN-937
>                 URL: https://issues.apache.org/jira/browse/YARN-937
>             Project: Hadoop YARN
>          Issue Type: Bug
>    Affects Versions: 2.1.0-beta
>            Reporter: Arun C Murthy
>            Assignee: Alejandro Abdelnur
>            Priority: Blocker
>             Fix For: 2.1.0-beta
>         Attachments: YARN-937.patch, YARN-937.patch
> Fix unmanaged AM in non-secure/secure setup post YARN-701 since app-tokens will be used
in both scenarios.

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