[
https://issues.apache.org/jira/browse/YARN-304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13949096#comment-13949096
]
Hadoop QA commented on YARN-304:
--------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12637103/YARN-304-1.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. There were no new javadoc warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:red}-1 findbugs{color}. The patch appears to introduce 1 new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/3472//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-YARN-Build/3472//artifact/trunk/patchprocess/newPatchFindbugsWarningshadoop-yarn-server-resourcemanager.html
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/3472//console
This message is automatically generated.
> RM Tracking Links for purged applications needs a long-term solution
> --------------------------------------------------------------------
>
> Key: YARN-304
> URL: https://issues.apache.org/jira/browse/YARN-304
> Project: Hadoop YARN
> Issue Type: Sub-task
> Affects Versions: 3.0.0, 0.23.5
> Reporter: Derek Dagit
> Assignee: Mayank Bansal
> Attachments: YARN-304-1.patch
>
>
> This JIRA is intended to track a proper long-term fix for the issue described
> in YARN-285.
> The following is from the original description:
> 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 was sent by Atlassian JIRA
(v6.2#6252)
