[jira] [Updated] (MAPREDUCE-3513) Capacity Scheduler web UI has a spelling mistake for Memory.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chackaravarthy updated MAPREDUCE-3513: -- Attachment: mapreduce-3513.patch Capacity Scheduler web UI has a spelling mistake for Memory. Key: MAPREDUCE-3513 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3513 Project: Hadoop Map/Reduce Issue Type: Bug Components: mrv2 Reporter: Mahadev konar Assignee: chackaravarthy Priority: Trivial Attachments: mapreduce-3513.patch The web page for capacity scheduler has a column named Memopry Total, a spelling mistake which needs to be fixed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (MAPREDUCE-3513) Capacity Scheduler web UI has a spelling mistake for Memory.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chackaravarthy updated MAPREDUCE-3513: -- Fix Version/s: 0.23.1 Affects Version/s: 0.23.0 Status: Patch Available (was: Open) Attached the patch for this. pls review. There is one more place where there is a spelling mistake : Node Manger instead of Node Manager. I checked for similar mistakes in the UI. I was able to identify these 2 only. Capacity Scheduler web UI has a spelling mistake for Memory. Key: MAPREDUCE-3513 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3513 Project: Hadoop Map/Reduce Issue Type: Bug Components: mrv2 Affects Versions: 0.23.0 Reporter: Mahadev konar Assignee: chackaravarthy Priority: Trivial Fix For: 0.23.1 Attachments: mapreduce-3513.patch The web page for capacity scheduler has a column named Memopry Total, a spelling mistake which needs to be fixed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (MAPREDUCE-3513) Capacity Scheduler web UI has a spelling mistake for Memory.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chackaravarthy updated MAPREDUCE-3513: -- Attachment: mapreduce-3513.patch @Mahadev , reuploading the patch granting license to ASF. pls check. Thanks Capacity Scheduler web UI has a spelling mistake for Memory. Key: MAPREDUCE-3513 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3513 Project: Hadoop Map/Reduce Issue Type: Bug Components: mrv2 Affects Versions: 0.23.0 Reporter: Mahadev konar Assignee: chackaravarthy Priority: Trivial Fix For: 0.23.1 Attachments: mapreduce-3513.patch, mapreduce-3513.patch The web page for capacity scheduler has a column named Memopry Total, a spelling mistake which needs to be fixed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (MAPREDUCE-3513) Capacity Scheduler web UI has a spelling mistake for Memory.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chackaravarthy updated MAPREDUCE-3513: -- Status: Patch Available (was: Open) Capacity Scheduler web UI has a spelling mistake for Memory. Key: MAPREDUCE-3513 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3513 Project: Hadoop Map/Reduce Issue Type: Bug Components: mrv2 Affects Versions: 0.23.0 Reporter: Mahadev konar Assignee: chackaravarthy Priority: Trivial Fix For: 0.23.1 Attachments: mapreduce-3513.patch, mapreduce-3513.patch The web page for capacity scheduler has a column named Memopry Total, a spelling mistake which needs to be fixed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (MAPREDUCE-3035) MR V2 jobhistory does not contain rack information
[ https://issues.apache.org/jira/browse/MAPREDUCE-3035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chackaravarthy updated MAPREDUCE-3035: -- Status: Patch Available (was: Open) MR V2 jobhistory does not contain rack information -- Key: MAPREDUCE-3035 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3035 Project: Hadoop Map/Reduce Issue Type: Bug Components: mrv2 Affects Versions: 0.23.0 Reporter: Karam Singh Assignee: chackaravarthy Priority: Blocker Fix For: 0.23.0 Attachments: MAPREDUCE-3035-1.patch, MAPREDUCE-3035.patch When topology.node.switch.mapping.impl is set to enable rack-locality resolution via the topology script, from the RM web-UI, we can see the rack information for each node. Running a job also reveals the information about rack-local map tasks launched at end of job completion on the client side. But the hostname field for attempts in the JobHistory does not contain this rack information. In case of hadoop-0.20 securiy or MRV1, hostname field of job history does contain rackid/hostname whereas in MRV2, hostname field only contains the hostIP. Thus this is a regression. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (MAPREDUCE-3009) RM UI - Applications - Application(Job History) - Map Tasks - Task ID - Node link is not working
[ https://issues.apache.org/jira/browse/MAPREDUCE-3009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chackaravarthy updated MAPREDUCE-3009: -- Attachment: MAPREDUCE-3009-1.patch RM UI - Applications - Application(Job History) - Map Tasks - Task ID - Node link is not working - Key: MAPREDUCE-3009 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3009 Project: Hadoop Map/Reduce Issue Type: Bug Components: jobhistoryserver, mrv2 Affects Versions: 0.23.0, 0.24.0 Reporter: chackaravarthy Assignee: chackaravarthy Fix For: 0.24.0 Attachments: IE_node_link_not_working.png, MAPREDUCE-3009-1.patch, MAPREDUCE-3009.patch, chrome_node_link_working.png, invalid_url.png, invalid_url_latest_code.png RM UI - Applications - Application(Job History) - Map Tasks - Task ID - Node link is not working. The URL contains extra '/' which is causing the problem. Please find in the attached screen shots. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (MAPREDUCE-3009) RM UI - Applications - Application(Job History) - Map Tasks - Task ID - Node link is not working
[ https://issues.apache.org/jira/browse/MAPREDUCE-3009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chackaravarthy updated MAPREDUCE-3009: -- Status: Patch Available (was: Open) Attached the patch. pls review. Thanks. RM UI - Applications - Application(Job History) - Map Tasks - Task ID - Node link is not working - Key: MAPREDUCE-3009 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3009 Project: Hadoop Map/Reduce Issue Type: Bug Components: jobhistoryserver, mrv2 Affects Versions: 0.23.0, 0.24.0 Reporter: chackaravarthy Assignee: chackaravarthy Fix For: 0.24.0 Attachments: IE_node_link_not_working.png, MAPREDUCE-3009-1.patch, MAPREDUCE-3009.patch, chrome_node_link_working.png, invalid_url.png, invalid_url_latest_code.png RM UI - Applications - Application(Job History) - Map Tasks - Task ID - Node link is not working. The URL contains extra '/' which is causing the problem. Please find in the attached screen shots. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (MAPREDUCE-3009) RM UI - Applications - Application(Job History) - Map Tasks - Task ID - Node link is not working
[ https://issues.apache.org/jira/browse/MAPREDUCE-3009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chackaravarthy updated MAPREDUCE-3009: -- Attachment: chrome_node_link_working.png IE_node_link_not_working.png Hi Vinod, As you said, there is a change in the latest code (ip address is replaced by host name) But still that problem exists. I see it as a Browser level problem. I was using InternetExplorer only earlier and hence added the screen shot for those. Now I checked in Chrome Browser and there its working fine. I am not sure how it will behave in FireFox. I have some problem in firefox installation in my system. So I have attached the screenshots for other 2 browsers (IE and Chrome) This issue exists in IE browser only. In chrome its working properly. Thanks RM UI - Applications - Application(Job History) - Map Tasks - Task ID - Node link is not working - Key: MAPREDUCE-3009 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3009 Project: Hadoop Map/Reduce Issue Type: Bug Components: jobhistoryserver, mrv2 Affects Versions: 0.23.0, 0.24.0 Reporter: chackaravarthy Assignee: chackaravarthy Fix For: 0.24.0 Attachments: IE_node_link_not_working.png, MAPREDUCE-3009.patch, chrome_node_link_working.png, invalid_url.png, invalid_url_latest_code.png RM UI - Applications - Application(Job History) - Map Tasks - Task ID - Node link is not working. The URL contains extra '/' which is causing the problem. Please find in the attached screen shots. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (MAPREDUCE-3035) MR V2 jobhistory does not contain rack information
[ https://issues.apache.org/jira/browse/MAPREDUCE-3035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chackaravarthy updated MAPREDUCE-3035: -- Status: Patch Available (was: Open) patch submitted. pls review. Thanks MR V2 jobhistory does not contain rack information -- Key: MAPREDUCE-3035 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3035 Project: Hadoop Map/Reduce Issue Type: Bug Components: mrv2 Affects Versions: 0.23.0 Reporter: Karam Singh Assignee: Devaraj K Priority: Blocker Fix For: 0.23.0 Attachments: MAPREDUCE-3035.patch When topology.node.switch.mapping.impl is set to enable rack-locality resolution via the topology script, from the RM web-UI, we can see the rack information for each node. Running a job also reveals the information about rack-local map tasks launched at end of job completion on the client side. But the hostname field for attempts in the JobHistory does not contain this rack information. In case of hadoop-0.20 securiy or MRV1, hostname field of job history does contain rackid/hostname whereas in MRV2, hostname field only contains the hostIP. Thus this is a regression. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (MAPREDUCE-3035) MR V2 jobhistory does not contain rack information
[ https://issues.apache.org/jira/browse/MAPREDUCE-3035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chackaravarthy updated MAPREDUCE-3035: -- Attachment: MAPREDUCE-3035.patch MR V2 jobhistory does not contain rack information -- Key: MAPREDUCE-3035 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3035 Project: Hadoop Map/Reduce Issue Type: Bug Components: mrv2 Affects Versions: 0.23.0 Reporter: Karam Singh Assignee: Devaraj K Priority: Blocker Fix For: 0.23.0 Attachments: MAPREDUCE-3035.patch When topology.node.switch.mapping.impl is set to enable rack-locality resolution via the topology script, from the RM web-UI, we can see the rack information for each node. Running a job also reveals the information about rack-local map tasks launched at end of job completion on the client side. But the hostname field for attempts in the JobHistory does not contain this rack information. In case of hadoop-0.20 securiy or MRV1, hostname field of job history does contain rackid/hostname whereas in MRV2, hostname field only contains the hostIP. Thus this is a regression. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (MAPREDUCE-3009) RM UI - Applications - Application(Job History) - Map Tasks - Task ID - Node link is not working
[ https://issues.apache.org/jira/browse/MAPREDUCE-3009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chackaravarthy updated MAPREDUCE-3009: -- Component/s: mrv2 RM UI - Applications - Application(Job History) - Map Tasks - Task ID - Node link is not working - Key: MAPREDUCE-3009 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3009 Project: Hadoop Map/Reduce Issue Type: Bug Components: jobhistoryserver, mrv2 Affects Versions: 0.23.0, 0.24.0 Reporter: chackaravarthy Fix For: 0.24.0 Attachments: MAPREDUCE-3009.patch, invalid_url.png, invalid_url_latest_code.png RM UI - Applications - Application(Job History) - Map Tasks - Task ID - Node link is not working. The URL contains extra '/' which is causing the problem. Please find in the attached screen shots. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
