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 0BC98E516 for ; Sat, 22 Dec 2012 01:59:13 +0000 (UTC) Received: (qmail 3581 invoked by uid 500); 22 Dec 2012 01:59:12 -0000 Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org Received: (qmail 3555 invoked by uid 500); 22 Dec 2012 01:59:12 -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 3544 invoked by uid 99); 22 Dec 2012 01:59:12 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 22 Dec 2012 01:59:12 +0000 Date: Sat, 22 Dec 2012 01:59:12 +0000 (UTC) From: "Vinod Kumar Vavilapalli (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (YARN-285) RM should be able to provide a tracking link for apps that have already been purged 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-285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13538644#comment-13538644 ] Vinod Kumar Vavilapalli commented on YARN-285: ---------------------------------------------- bq. I just committed this to trunk and branch-0.23. Thanks Derek! Also branch-2. > RM should be able to provide a tracking link for apps that have already been purged > ----------------------------------------------------------------------------------- > > Key: YARN-285 > URL: https://issues.apache.org/jira/browse/YARN-285 > Project: Hadoop YARN > Issue Type: Improvement > Affects Versions: 3.0.0, 0.23.5 > Reporter: Derek Dagit > Assignee: Derek Dagit > Fix For: 2.0.3-alpha, 0.23.6 > > Attachments: YARN-285-branch-0.23.patch, YARN-285-branch-0.23.patch, YARN-285-branch-0.23.patch, YARN-285-branch-0.23.patch, YARN-285.patch, YARN-285.patch, YARN-285.patch, YARN-285.patch > > > As applications complete, the RM tracks their IDs in a completed list. This list is routinely truncated to limit the total number of application remembered by the RM. > When a user clicks the History for a job, either the browser is redirected to the application's tracking link obtained from the stored application instance. But when the application has been purged from the RM, an error is displayed. > In very busy clusters the rate at which applications complete can cause applications to be purged from the RM's internal list within hours, which breaks the proxy URLs users have saved for their jobs. > We would like the RM to provide valid tracking links persist so that users are not frustrated by broken links. -- 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