[
https://issues.apache.org/jira/browse/YARN-571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13638481#comment-13638481
]
Vinod Kumar Vavilapalli commented on YARN-571:
----------------------------------------------
bq. Also, the user could be part of the token only, instead of including it in
Container, or is this not possible at the moment because the ContainerToken is
not available in non-secure mode.
That's correct, not possible at the moment.
I'll update the patch..
> User should not be part of ContainerLaunchContext
> -------------------------------------------------
>
> Key: YARN-571
> URL: https://issues.apache.org/jira/browse/YARN-571
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Hitesh Shah
> Assignee: Vinod Kumar Vavilapalli
> Attachments: YARN-571-20130415.2.txt, YARN-571-20130418.txt
>
>
> Today, a user is expected to set the user name in the CLC when either
> submitting an application or launching a container from the AM. This does not
> make sense as the user can/has been identified by the RM as part of the RPC
> layer.
> Solution would be to move the user information into either the Container
> object or directly into the ContainerToken which can then be used by the NM
> to launch the container. This user information would set into the container
> by the RM.
--
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
