[
https://issues.apache.org/jira/browse/HADOOP-7030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13235866#comment-13235866
]
Steve Loughran commented on HADOOP-7030:
----------------------------------------
#the accessors are good for testing.
#I've been slowly putting the changes into the code, but gradually and trying
to avoid any form of problem w/existing custom topologies.
What I do want to do -and they arent a jiras, I should add them are
* A command line entry point to take a list of hostnames, look at the current
config, tell you what they map to and list the final map. This lets you
preflight check the operations.
* A way of getting the dump of the topo map in use by a service, such as
through one of the JSP pages. That way people can see what's gone wrong.
Being able to get into the map is what you need for these.
> 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: Tom White
> Attachments: HADOOP-7030-2.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
