Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-issues@hadoop.apache.org
Date: Mon, 4 Mar 2013 19:47:13 +0000 (UTC)
From: "Jonathan Eagles (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12616809.1353358634161.377256.1362426433518@arcas>
In-Reply-To: <JIRA.12616809.1353358634161@arcas>
References: <JIRA.12616809.1353358634161@arcas>
Subject: [jira] [Commented] (YARN-227) Application expiration difficult to
 debug for end-users
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Jonathan Eagles commented on YARN-227:
--------------------------------------

+1. Jason. If you can provide a 23 patch, I can check the code in there too.
                
> Application expiration difficult to debug for end-users
> -------------------------------------------------------
>
>                 Key: YARN-227
>                 URL: https://issues.apache.org/jira/browse/YARN-227
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: resourcemanager
>    Affects Versions: 0.23.3, 2.0.1-alpha
>            Reporter: Jason Lowe
>            Assignee: Jason Lowe
>              Labels: usability
>         Attachments: YARN-227.patch
>
>
> When an AM attempt expires the AMLivelinessMonitor in the RM will kill the job and mark it as failed.  However there are no diagnostic messages set for the application indicating that the application failed because of expiration.  Even if the AM logs are examined, it's often not obvious that the application was externally killed.  The only evidence of what happened to the application is currently in the RM logs, and those are often not accessible by users.

--
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