[
https://issues.apache.org/jira/browse/YARN-571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinod Kumar Vavilapalli updated YARN-571:
-----------------------------------------
Attachment: YARN-571-20130415.2.txt
Here's a patch that fixes this:
- Moved user from ContainerLaunchContext into Container
- RM gets user-name from client connection as part of submit-app, sends to AM
as part of Container and NM validates the user-name from the Container using
ContainerToken.
- Changed ApplicationStateData to also persist user-name.
- Modified DistributedShell and MR App also to reflect these changes.
- Fixed existing tests.
- Modified TestContainerManagerSecurity to validate the user-name being passed
around.
> 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
>
>
> 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
