[
https://issues.apache.org/jira/browse/YARN-1859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13944069#comment-13944069
]
Hudson commented on YARN-1859:
------------------------------
SUCCESS: Integrated in Hadoop-Hdfs-trunk #1709 (See
[https://builds.apache.org/job/Hadoop-Hdfs-trunk/1709/])
YARN-1863. Fixed test failure in TestRMFailover after YARN-1859. Contributed by
Xuan Gong. (vinodkv:
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1580094)
* /hadoop/common/trunk/hadoop-yarn-project/CHANGES.txt
*
/hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-client/src/test/java/org/apache/hadoop/yarn/client/TestRMFailover.java
> WebAppProxyServlet will throw ApplicationNotFoundException if the app is no
> longer cached in RM
> -----------------------------------------------------------------------------------------------
>
> Key: YARN-1859
> URL: https://issues.apache.org/jira/browse/YARN-1859
> Project: Hadoop YARN
> Issue Type: Bug
> Reporter: Zhijie Shen
> Assignee: Zhijie Shen
> Fix For: 2.4.0
>
> Attachments: YARN-1859.1.patch
>
>
> WebAppProxyServlet checks null to determine whether the application is not
> found or not.
> {code}
> ApplicationReport applicationReport = getApplicationReport(id);
> if(applicationReport == null) {
> LOG.warn(req.getRemoteUser()+" Attempting to access "+id+
> " that was not found");
> {code}
> However, WebAppProxyServlet calls AppReportFetcher, which consequently calls
> ClientRMService. When application is not found, ClientRMService throws
> ApplicationNotFoundException. Therefore, in WebAppProxyServlet, the following
> logic to create the tracking url for a non-cached app will no longer be in
> use.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
