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-610) ClientToken should not be set in the environment
Date Sun, 16 Jun 2013 03:43:20 GMT

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

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

bq. Now instead of sharing it here in environment we should send it on AMRMProtocol as a part
of AMRegistration. Thereby AM will get secret key after am registration and will be able to
authenticate thereafter. any thoughts?
That is reasonable.

Seems like the patch has gone stale, can you rebase?

File a MR ticket too as a followup tracking MR changes.

Patch looks mostly good. W.r.t TestClientTokens
 - TestClientTokens should also be renamed to TestClientToAMTokens
 - CustomNM is no longer needed?
 - There is commented out code that should be removed.
                
> ClientToken should not be set in the environment
> ------------------------------------------------
>
>                 Key: YARN-610
>                 URL: https://issues.apache.org/jira/browse/YARN-610
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>            Reporter: Siddharth Seth
>            Assignee: Omkar Vinit Joshi
>         Attachments: YARN-610-20130614.patch
>
>
> Similar to YARN-579, this can be set via ContainerTokens

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