[
https://issues.apache.org/jira/browse/HADOOP-7030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13002252#comment-13002252
]
Patrick Angeles commented on HADOOP-7030:
-----------------------------------------
- Could you combine the two types of file, so that if there are three columns
the first two are interpreted as a range, otherwise use the first as a single
host. Or just support CIDR notation?
- I'd prefer to keep them separate as the first two columns have completely
different meanings when using one style (table lookup) over the other
(IP-range).
BTW, I don't think CIDR is appropriate here. For the table-based mapping, you
can get either hosts or IPs, possibly depending on who (JT or NN) is requesting
the rack ID. The docs are unclear here.
In either case, servers within a rack rarely fall in units that are powers of
two.
> new topology mapping implementations
> ------------------------------------
>
> 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: Patrick Angeles
> Attachments: HADOOP-7030-2.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.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
