[
https://issues.apache.org/jira/browse/HADOOP-7030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13284630#comment-13284630
]
Matt Foley edited comment on HADOOP-7030 at 5/29/12 6:38 AM:
-------------------------------------------------------------
Patch not committed in time for 1.1.0.
was (Author: mattf):
Patch not submitted in time for 1.1.0.
> Add TableMapping topology implementation to read host to rack mapping from a
> file
> ---------------------------------------------------------------------------------
>
> Key: HADOOP-7030
> URL: https://issues.apache.org/jira/browse/HADOOP-7030
> Project: Hadoop Common
> Issue Type: New Feature
> Affects Versions: 0.20.1, 0.20.2, 0.21.0
> Reporter: Patrick Angeles
> Assignee: Tom White
> Fix For: 2.0.0-alpha
>
> Attachments: HADOOP-7030-2.patch, HADOOP-7030-branch-1.patch,
> HADOOP-7030.patch, HADOOP-7030.patch, HADOOP-7030.patch, HADOOP-7030.patch,
> topology.patch
>
>
> The default ScriptBasedMapping implementation of DNSToSwitchMapping for
> determining cluster topology has some drawbacks. Principally, it forks to an
> OS-specific script.
> This issue proposes two new Java implementations of DNSToSwitchMapping.
> TableMapping reads a two column text file that maps an IP or hostname to a
> rack ID. Ip4RangeMapping reads a three column text file where each line
> represents a start and end IP range plus a rack ID.
--
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