[ https://issues.apache.org/jira/browse/YARN-3967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14641522#comment-14641522 ]
Hudson commented on YARN-3967: ------------------------------ FAILURE: Integrated in Hadoop-Yarn-trunk #997 (See [https://builds.apache.org/job/Hadoop-Yarn-trunk/997/]) YARN-3967. Fetch the application report from the AHS if the RM does not (xgong: rev fbd6063269221ec25834684477f434e19f0b66af) * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-web-proxy/src/main/java/org/apache/hadoop/yarn/server/webproxy/AppReportFetcher.java * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-web-proxy/src/test/java/org/apache/hadoop/yarn/server/webproxy/TestAppReportFetcher.java * hadoop-yarn-project/CHANGES.txt > Fetch the application report from the AHS if the RM does not know about it > -------------------------------------------------------------------------- > > Key: YARN-3967 > URL: https://issues.apache.org/jira/browse/YARN-3967 > Project: Hadoop YARN > Issue Type: Bug > Affects Versions: 2.7.1 > Reporter: Mit Desai > Assignee: Mit Desai > Fix For: 2.7.2 > > Attachments: YARN-3967.1.patch, YARN-3967.2.patch, YARN-3967.3.patch > > > If the application history service has been enabled and RM has forgotten > anout an application, try and fetch the app report form the AHS. > On larger clusters, the RM can forget about the applications in about 30 > minutes. The proxy url generated during the job submission will try to fetch > the app report from the RM and will fail to get anything from there. If the > app is not found in the RM, we will need to get the application report from > the Application History Server (if it is enabled) to see if we can get any > information on that application before throwing an exception. -- This message was sent by Atlassian JIRA (v6.3.4#6332)