[
https://issues.apache.org/jira/browse/MAPREDUCE-3035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinod Kumar Vavilapalli updated MAPREDUCE-3035:
-----------------------------------------------
Attachment: MAPREDUCE-3035-20111031.1.txt
Attaching updated patch:
- Removed bugs related to multiple resolution of racks.
- Made rumen related changes as suggested by Amar in the above comments
- Fixed test to verify that the rack-name is getting logged properly in the
JobHistoryServer
[~ravidotg] is helping me test this with Rumen.
> 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: Critical
> Fix For: 0.23.1
>
> Attachments: MAPREDUCE-3035-1.patch, MAPREDUCE-3035-20111031.1.txt,
> 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
