Return-Path: X-Original-To: apmail-hadoop-yarn-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-yarn-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 6DA091009C for ; Tue, 23 Jul 2013 13:12:52 +0000 (UTC) Received: (qmail 88142 invoked by uid 500); 23 Jul 2013 13:12:52 -0000 Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org Received: (qmail 87993 invoked by uid 500); 23 Jul 2013 13:12:50 -0000 Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: yarn-issues@hadoop.apache.org Delivered-To: mailing list yarn-issues@hadoop.apache.org Received: (qmail 87973 invoked by uid 99); 23 Jul 2013 13:12:49 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 23 Jul 2013 13:12:49 +0000 Date: Tue, 23 Jul 2013 13:12:49 +0000 (UTC) From: "Alejandro Abdelnur (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (YARN-937) Fix unmanaged AM in non-secure/secure setup post YARN-701 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/YARN-937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13716372#comment-13716372 ] Alejandro Abdelnur commented on YARN-937: ----------------------------------------- [~bikassaha], in the way I've using unmanaged AM I have a running service that hosts the AM without forking a process. IMO, this is the powerful thing about unmanaged AMs. If I would be to fork a new process to run the AM, why would I just use a managed AM. [~daryn], the AM launcher, after creating an APP, forks a process to register it to the schedulers, the new process does not have the launch context thus we need the token file in this case. > Fix unmanaged AM in non-secure/secure setup post YARN-701 > --------------------------------------------------------- > > Key: YARN-937 > URL: https://issues.apache.org/jira/browse/YARN-937 > Project: Hadoop YARN > Issue Type: Bug > Affects Versions: 2.1.0-beta > Reporter: Arun C Murthy > Assignee: Alejandro Abdelnur > Priority: Blocker > Fix For: 2.1.0-beta > > Attachments: YARN-937.patch, YARN-937.patch > > > Fix unmanaged AM in non-secure/secure setup post YARN-701 since app-tokens will be used in both scenarios. -- 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