[
https://issues.apache.org/jira/browse/MAPREDUCE-4105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ahmed Radwan updated MAPREDUCE-4105:
------------------------------------
Attachment: MAPREDUCE-4105_rev2.patch
Thanks Tom!
I have updated the patch per your comments. Regarding the static state of the
RackResolver, I can see that the main hadoop-project/pom.xml has
<forkMode>always</forkMode> as part of surefire configuration, which means that
each test class will have separate jvm. So this shouldn't be an issue, what so
you think? I think having such stateful RackResolver might be advantageous in
prevent changing the mappings, etc within the same jvm, so we can leave it as
long as tests are fine.
> Yarn RackResolver ignores rack configurations
> ---------------------------------------------
>
> Key: MAPREDUCE-4105
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4105
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: mrv2
> Affects Versions: 0.23.1
> Reporter: Ahmed Radwan
> Assignee: Ahmed Radwan
> Fix For: 0.23.2
>
> Attachments: MAPREDUCE-4105.patch, MAPREDUCE-4105_rev2.patch
>
>
> Incorrect mappings because the Yarn RackResolver ignores rack configurations.
> This can be verified by inspecting the resource manager web ui that lists all
> the nodes, all of them show up with /default-rack regardless of the output
> from the script specified using net.topology.script.file.name configuration
> property.
--
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
