[
https://issues.apache.org/jira/browse/HADOOP-1985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Devaraj Das updated HADOOP-1985:
--------------------------------
Attachment: 1985.v19.patch
Attaching one version of the revised patch. The changes from the previous patch
are:
1) The conditional code depending on whether the framework is running under
junit has been removed.
2) NetUtils has some APIs to store & retrieve static resolutions (foo.bar.com
-> localhost). This comes handy for tests to do with racks.
3) On the DFS side of things, a new command DNA_BLOCKREPORT has been added. Now
a datanode will waste at most one block report. It can potentially succeed in
its first block report (if the namenode finished resolving the rackID for the
datanode before that).
4) Batch resolution API has been added to DNSToSwitchMapping interface.
This patch passes 'ant test'. I am in the process of doing testing on a big
cluster.
> Abstract node to switch mapping into a topology service class used by
> namenode and jobtracker
> ---------------------------------------------------------------------------------------------
>
> Key: HADOOP-1985
> URL: https://issues.apache.org/jira/browse/HADOOP-1985
> Project: Hadoop Core
> Issue Type: New Feature
> Components: dfs, mapred
> Reporter: eric baldeschwieler
> Assignee: Devaraj Das
> Fix For: 0.17.0
>
> Attachments: 1985.new.patch, 1985.v1.patch, 1985.v10.patch,
> 1985.v11.patch, 1985.v19.patch, 1985.v2.patch, 1985.v3.patch, 1985.v4.patch,
> 1985.v5.patch, 1985.v6.patch, 1985.v9.patch, jobinprogress.patch
>
>
> In order to implement switch locality in MapReduce, we need to have switch
> location in both the namenode and job tracker. Currently the namenode asks
> the data nodes for this info and they run a local script to answer this
> question. In our environment and others that I know of there is no reason to
> push this to each node. It is easier to maintain a centralized script that
> maps node DNS names to switch strings.
> I propose that we build a new class that caches known DNS name to switch
> mappings and invokes a loadable class or a configurable system call to
> resolve unknown DNS to switch mappings. We can then add this to the namenode
> to support the current block to switch mapping needs and simplify the data
> nodes. We can also add this same callout to the job tracker and then
> implement rack locality logic there without needing to chane the filesystem
> API or the split planning API.
> Not only is this the least intrusive path to building racklocal MR I can ID,
> it is also future compatible to future infrastructures that may derive
> topology on the fly, etc, etc...
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
