[jira] [Updated] (YARN-5041) application master log can not be available when clicking jobhistory's am logs link
[ https://issues.apache.org/jira/browse/YARN-5041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haibo Chen updated YARN-5041: - Attachment: yarn5041.002.patch Thanks for letting me know. The test failures were indeed caused by my change. Updated the patch to fix the failures. > application master log can not be available when clicking jobhistory's am > logs link > --- > > Key: YARN-5041 > URL: https://issues.apache.org/jira/browse/YARN-5041 > Project: Hadoop YARN > Issue Type: Bug > Components: yarn >Affects Versions: 2.9.0 >Reporter: chenyukang >Assignee: Haibo Chen >Priority: Critical > Attachments: yarn5041.001.patch, yarn5041.002.patch > > > In history server webapp, application master logs link is wrong. it shows "No > logs available for container container_1462419429440_0003_01_01". It > direct to a wrong nodemanager http port instead of a node manager' container > managerment port. I think YARN-4701 brought this bug -- 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-5041) application master log can not be available when clicking jobhistory's am logs link
[ https://issues.apache.org/jira/browse/YARN-5041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haibo Chen updated YARN-5041: - Attachment: yarn5041.001.patch The patch is tested locally. IMO, the unit test is too difficult to create given that the render() of HsJobBlock calls a lot of methods that calls injector. Any suggestion of how to unit test this will be appreciated. > application master log can not be available when clicking jobhistory's am > logs link > --- > > Key: YARN-5041 > URL: https://issues.apache.org/jira/browse/YARN-5041 > Project: Hadoop YARN > Issue Type: Bug > Components: yarn >Affects Versions: 2.9.0 >Reporter: chenyukang >Assignee: Haibo Chen >Priority: Critical > Attachments: yarn5041.001.patch > > > In history server webapp, application master logs link is wrong. it shows "No > logs available for container container_1462419429440_0003_01_01". It > direct to a wrong nodemanager http port instead of a node manager' container > managerment port. I think YARN-4701 brought this bug -- 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-5041) application master log can not be available when clicking jobhistory's am logs link
[ https://issues.apache.org/jira/browse/YARN-5041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Kanter updated YARN-5041: Priority: Critical (was: Major) > application master log can not be available when clicking jobhistory's am > logs link > --- > > Key: YARN-5041 > URL: https://issues.apache.org/jira/browse/YARN-5041 > Project: Hadoop YARN > Issue Type: Bug > Components: yarn >Affects Versions: 2.9.0 >Reporter: chenyukang >Assignee: Haibo Chen >Priority: Critical > > In history server webapp, application master logs link is wrong. it shows "No > logs available for container container_1462419429440_0003_01_01". It > direct to a wrong nodemanager http port instead of a node manager' container > managerment port. I think YARN-4701 brought this bug -- 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-5041) application master log can not be available when clicking jobhistory's am logs link
[ https://issues.apache.org/jira/browse/YARN-5041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Lowe updated YARN-5041: - Target Version/s: 2.9.0 Fix Version/s: (was: 3.0.0) It would be a significant regression if jobhistory AM log links no longer work after YARN-4701. [~haibochen] or [~rkanter] could you take a look? > application master log can not be available when clicking jobhistory's am > logs link > --- > > Key: YARN-5041 > URL: https://issues.apache.org/jira/browse/YARN-5041 > Project: Hadoop YARN > Issue Type: Bug > Components: yarn >Affects Versions: 2.9.0 >Reporter: chenyukang > > In history server webapp, application master logs link is wrong. it shows "No > logs available for container container_1462419429440_0003_01_01". It > direct to a wrong nodemanager http port instead of a node manager' container > managerment port. I think YARN-4701 brought this bug -- 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-5041) application master log can not be available when clicking jobhistory's am logs link
[ https://issues.apache.org/jira/browse/YARN-5041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenyukang updated YARN-5041: - Description: In history server webapp, application master logs link is wrong. it shows "No logs available for container container_1462419429440_0003_01_01". It direct to a wrong nodemanager http port instead of a node manager' container managerment port. I think YARN-4701 brought this bug (was: In history server webapp, application master logs link is wrong. It direct to a wrong nodemanager http port instead of a node manager' container managerment port. I think YARN-4701 brought this bug) > application master log can not be available when clicking jobhistory's am > logs link > --- > > Key: YARN-5041 > URL: https://issues.apache.org/jira/browse/YARN-5041 > Project: Hadoop YARN > Issue Type: Bug > Components: yarn >Affects Versions: 2.9.0 >Reporter: chenyukang > Fix For: 3.0.0 > > > In history server webapp, application master logs link is wrong. it shows "No > logs available for container container_1462419429440_0003_01_01". It > direct to a wrong nodemanager http port instead of a node manager' container > managerment port. I think YARN-4701 brought this bug -- 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-5041) application master log can not be available when clicking jobhistory's am logs link
[ https://issues.apache.org/jira/browse/YARN-5041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenyukang updated YARN-5041: - Flags: Patch,Important (was: Important) Fix Version/s: 3.0.0 > application master log can not be available when clicking jobhistory's am > logs link > --- > > Key: YARN-5041 > URL: https://issues.apache.org/jira/browse/YARN-5041 > Project: Hadoop YARN > Issue Type: Bug > Components: yarn >Affects Versions: 2.9.0 >Reporter: chenyukang > Fix For: 3.0.0 > > > In history server webapp, application master logs link is wrong. It direct to > a wrong nodemanager http port instead of a node manager' container > managerment port. I think YARN-4701 brought this bug -- 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
