Return-Path: X-Original-To: apmail-hadoop-yarn-dev-archive@minotaur.apache.org Delivered-To: apmail-hadoop-yarn-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 11033D1EF for ; Wed, 22 May 2013 17:16:30 +0000 (UTC) Received: (qmail 18394 invoked by uid 500); 22 May 2013 17:16:27 -0000 Delivered-To: apmail-hadoop-yarn-dev-archive@hadoop.apache.org Received: (qmail 17892 invoked by uid 500); 22 May 2013 17:16:26 -0000 Mailing-List: contact yarn-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: yarn-dev@hadoop.apache.org Delivered-To: mailing list yarn-dev@hadoop.apache.org Received: (qmail 17695 invoked by uid 99); 22 May 2013 17:16:24 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 22 May 2013 17:16:24 +0000 Date: Wed, 22 May 2013 17:16:24 +0000 (UTC) From: "Omkar Vinit Joshi (JIRA)" To: yarn-dev@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (YARN-718) Remove RemoteUGI.getRemoteUser check from startContainer in ContainerManagerImpl as this is no longer required MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Omkar Vinit Joshi created YARN-718: -------------------------------------- Summary: Remove RemoteUGI.getRemoteUser check from startContainer in ContainerManagerImpl as this is no longer required Key: YARN-718 URL: https://issues.apache.org/jira/browse/YARN-718 Project: Hadoop YARN Issue Type: Bug Reporter: Omkar Vinit Joshi Assignee: Omkar Vinit Joshi Earlier there was a check in startContainer which was validating that RemoteUGI.getRemoteUser is same as containerId. However this check is no longer required and it should be removed. YARN-699 and YARN-715 will get fixed with this. -- 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