hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vinod Kumar Vavilapalli (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-937) Fix unmanaged AM in non-secure/secure setup post YARN-701
Date Mon, 22 Jul 2013 18:22:50 GMT

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

Vinod Kumar Vavilapalli commented on YARN-937:
----------------------------------------------

The thing is throughout YARN, and from my other conversations with [~daryn] on other tickets
in larger Hadoop, we are trying to move to digest auth irrespective of kerberos. In your latest
solution, unmanaged AMs in unsecure mode will not need any auth, which will regress that path.
Your first solution of sending across AMRMToken seems fine to me, we should just mark that
API as @Private.
                
> 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
>
>
> 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

Mime
View raw message