hadoop-hdfs-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eli Collins (Created) (JIRA)" <j...@apache.org>
Subject [jira] [Created] (HDFS-3146) Datanode should be able to register multiple network interfaces
Date Sun, 25 Mar 2012 21:12:27 GMT
Datanode should be able to register multiple network interfaces
---------------------------------------------------------------

                 Key: HDFS-3146
                 URL: https://issues.apache.org/jira/browse/HDFS-3146
             Project: Hadoop HDFS
          Issue Type: Sub-task
          Components: data-node
            Reporter: Eli Collins
            Assignee: Eli Collins


The Datanode should register multiple interfaces with the Namenode (who then forwards them
to clients). We can do this by extending the DatanodeID, which currently just contains a single
interface, to contain a list of interfaces. For compatibility, the DatanodeID method to get
the DN address for data transfer should remain unchanged (multiple interfaces are only used
where the client explicitly takes advantage of them).

By default, if the Datanode binds on all interfaces (via using the wildcard in the dfs*address
configuration) all interfaces are exposed, modulo ones like the loopback that should never
be exposed. Alternatively, a new configuration parameter ({{dfs.datanode.available.interfaces}})
allows the set of interfaces can be specified explicitly in case the user only wants to expose
a subset. If the new default behavior is too disruptive we could default dfs.datanode.available.interfaces
to be the IP of the IPC interface which is the only interface exposed today (per HADOOP-6867,
only the port from dfs.datanode.address is used today). 

The interfaces can be specified by name (eg "eth0"), subinterface name (eg "eth0:0"), or IP
address. The IP address can be specified by range using CIDR notation so the configuration
values are portable.

--
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

        

Mime
View raw message