You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Tom White (Updated) (JIRA)" <ji...@apache.org> on 2012/03/21 23:27:43 UTC

[jira] [Updated] (HADOOP-7030) new topology mapping implementations

     [ https://issues.apache.org/jira/browse/HADOOP-7030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tom White updated HADOOP-7030:
------------------------------

    Attachment: HADOOP-7030.patch

I've created a simplified patch which only has the two-column layout (we can add the range variant later as needed - also, now we have Guava the implementation will be simplified since we won't need to model IP addresses). I've also removed the refreshable interface, since as Steve notes it doesn't work well with the way that resolvers currently use the mapping interface (that should be revisited too).

In addition to the unit tests provided by Patrick, I tested on a small cluster and observed that the rack mappings I specified were picked up correctly.
                
> 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, 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