Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-issues@hadoop.apache.org
Date: Fri, 26 Oct 2012 16:07:12 +0000 (UTC)
From: "Jason Lowe (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <2142375321.32477.1351267632598.JavaMail.jiratomcat@arcas>
In-Reply-To: <1115164109.59700.1350502323858.JavaMail.jiratomcat@arcas>
Subject: [jira] [Updated] (YARN-165) RM should point tracking URL to RM web
 page for app when AM fails
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Jason Lowe updated YARN-165:
----------------------------

    Attachment: YARN-165.patch

Patch to change the tracking URL to point to the RM app page when the AM fails.
                
> RM should point tracking URL to RM web page for app when AM fails
> -----------------------------------------------------------------
>
>                 Key: YARN-165
>                 URL: https://issues.apache.org/jira/browse/YARN-165
>             Project: Hadoop YARN
>          Issue Type: Improvement
>          Components: resourcemanager
>    Affects Versions: 2.0.3-alpha, 0.23.5
>            Reporter: Jason Lowe
>            Priority: Blocker
>         Attachments: YARN-165.patch
>
>
> Currently when an ApplicationMaster fails the ResourceManager is updating the tracking URL to an empty string, see RMAppAttemptImpl.ContainerFinishedTransition.  Unfortunately when the client attempts to follow the proxy URL it results in a web page showing an HTTP 500 error and an ugly backtrace because "http://" isn't a very helpful tracking URL.
> It would be much more helpful if the proxy URL redirected to the RM webapp page for the specific application.  That page shows the various AM attempts and pointers to their logs which will be useful for debugging the problems that caused the AM attempts to fail.

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