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 12EA5102DD for ; Mon, 17 Mar 2014 18:29:48 +0000 (UTC) Received: (qmail 11637 invoked by uid 500); 17 Mar 2014 18:29:45 -0000 Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org Received: (qmail 11534 invoked by uid 500); 17 Mar 2014 18:29:45 -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 11515 invoked by uid 99); 17 Mar 2014 18:29:44 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 17 Mar 2014 18:29:44 +0000 Date: Mon, 17 Mar 2014 18:29:44 +0000 (UTC) From: "Naren Koneru (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (YARN-1577) Unmanaged AM is broken because of YARN-1493 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-1577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13938170#comment-13938170 ] Naren Koneru commented on YARN-1577: ------------------------------------ Sorry guys, been busy with some internal release stuff here. Will try to get it later today and if I cannot, will find someone to fix it...Thanks !... > Unmanaged AM is broken because of YARN-1493 > ------------------------------------------- > > Key: YARN-1577 > URL: https://issues.apache.org/jira/browse/YARN-1577 > Project: Hadoop YARN > Issue Type: Sub-task > Affects Versions: 2.3.0 > Reporter: Jian He > Assignee: Naren Koneru > Priority: Blocker > > Today unmanaged AM client is waiting for app state to be Accepted to launch the AM. This is broken since we changed in YARN-1493 to start the attempt after the application is Accepted. We may need to introduce an attempt state report that client can rely on to query the attempt state and choose to launch the unmanaged AM. -- This message was sent by Atlassian JIRA (v6.2#6252)