Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-issues@hadoop.apache.org
Date: Thu, 23 May 2013 22:25:20 +0000 (UTC)
From: "Omkar Vinit Joshi (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12642286.1365789374172.14286.1369347920458@arcas>
In-Reply-To: <JIRA.12642286.1365789374172@arcas>
References: <JIRA.12642286.1365789374172@arcas>
Subject: [jira] [Updated] (YARN-571) User should not be part of
 ContainerLaunchContext
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/YARN-571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Omkar Vinit Joshi updated YARN-571:
-----------------------------------

    Attachment: YARN-571.20130522.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: Omkar Vinit Joshi
>         Attachments: YARN-571-20130415.2.txt, YARN-571-20130418.txt, 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