[jira] [Updated] (YARN-3967) Fetch the application report from the AHS if the RM does not know about it
[ https://issues.apache.org/jira/browse/YARN-3967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-3967: - Fix Version/s: 2.8.0 > 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.8.0, 2.7.2, 3.0.0-alpha1 > > 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) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-3967) Fetch the application report from the AHS if the RM does not know about it
[ https://issues.apache.org/jira/browse/YARN-3967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mit Desai updated YARN-3967: Attachment: YARN-3967.3.patch Refined the patch [~xgong], I actually tried doing that before. But historyManager is a final member and cannot be initialiez outside. So it is not possible to make that change. There are 2 constructors for this class so initialization will have to be in 2 places. 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 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)
[jira] [Updated] (YARN-3967) Fetch the application report from the AHS if the RM does not know about it
[ https://issues.apache.org/jira/browse/YARN-3967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mit Desai updated YARN-3967: Attachment: YARN-3967.2.patch Fixed checkstyle and whitespaces 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 Attachments: YARN-3967.1.patch, YARN-3967.2.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)
[jira] [Updated] (YARN-3967) Fetch the application report from the AHS if the RM does not know about it
[ https://issues.apache.org/jira/browse/YARN-3967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mit Desai updated YARN-3967: Attachment: YARN-3967.1.patch Attaching the patch 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 Attachments: YARN-3967.1.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)
