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

Hadoop QA commented on YARN-571:
--------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  
http://issues.apache.org/jira/secure/attachment/12584780/YARN-571.20130522.2-branch-2.patch
  against trunk revision .

    {color:red}-1 patch{color}.  The patch command could not apply the patch.

Console output: https://builds.apache.org/job/PreCommit-YARN-Build/1004//console

This message is automatically generated.
                
> 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: Omkar Vinit Joshi
>         Attachments: YARN-571-20130415.2.txt, YARN-571-20130418.txt, 
> YARN-571.20130522.1.patch, YARN-571.20130522.2-branch-2.patch, 
> YARN-571.20130522.2.patch, YARN-571.20130522.patch
>
>
> 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

Reply via email to