From hdfs-issues-return-37909-apmail-hadoop-hdfs-issues-archive=hadoop.apache.org@hadoop.apache.org Mon Apr 2 19:09:47 2012 Return-Path: X-Original-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 602DB97C8 for ; Mon, 2 Apr 2012 19:09:47 +0000 (UTC) Received: (qmail 89903 invoked by uid 500); 2 Apr 2012 19:09:47 -0000 Delivered-To: apmail-hadoop-hdfs-issues-archive@hadoop.apache.org Received: (qmail 89868 invoked by uid 500); 2 Apr 2012 19:09:47 -0000 Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hdfs-issues@hadoop.apache.org Delivered-To: mailing list hdfs-issues@hadoop.apache.org Received: (qmail 89860 invoked by uid 99); 2 Apr 2012 19:09:47 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 02 Apr 2012 19:09:47 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=5.0 tests=ALL_TRUSTED,T_RP_MATCHES_RCVD X-Spam-Check-By: apache.org Received: from [140.211.11.116] (HELO hel.zones.apache.org) (140.211.11.116) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 02 Apr 2012 19:09:44 +0000 Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116]) by hel.zones.apache.org (Postfix) with ESMTP id 28313354BE3 for ; Mon, 2 Apr 2012 19:09:23 +0000 (UTC) Date: Mon, 2 Apr 2012 19:09:23 +0000 (UTC) From: "Hudson (Commented) (JIRA)" To: hdfs-issues@hadoop.apache.org Message-ID: <1770720348.2166.1333393763165.JavaMail.tomcat@hel.zones.apache.org> In-Reply-To: <1799485314.15261.1332710068300.JavaMail.tomcat@hel.zones.apache.org> Subject: [jira] [Commented] (HDFS-3148) The client should be able to use multiple local interfaces for data transfer MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HDFS-3148?page=3Dcom.atlassian.= jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D13244= 467#comment-13244467 ]=20 Hudson commented on HDFS-3148: ------------------------------ Integrated in Hadoop-Mapreduce-trunk-Commit #1982 (See [https://builds.apac= he.org/job/Hadoop-Mapreduce-trunk-Commit/1982/]) HADOOP-8210. Common side of HDFS-3148: The client should be able to use= multiple local interfaces for data transfer. Contributed by Eli Collins (R= evision 1308457) Result =3D FAILURE eli : http://svn.apache.org/viewcvs.cgi/?root=3DApache-SVN&view=3Drev&rev= =3D1308457 Files :=20 * /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt * /hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/java/or= g/apache/hadoop/net/DNS.java * /hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/java/or= g/apache/hadoop/net/NetUtils.java =20 > The client should be able to use multiple local interfaces for data trans= fer > -------------------------------------------------------------------------= --- > > Key: HDFS-3148 > URL: https://issues.apache.org/jira/browse/HDFS-3148 > Project: Hadoop HDFS > Issue Type: Sub-task > Components: hdfs client > Reporter: Eli Collins > Assignee: Eli Collins > Attachments: hdfs-3148-b1.txt, hdfs-3148-b1.txt, hdfs-3148.txt, h= dfs-3148.txt, hdfs-3148.txt > > > HDFS-3147 covers using multiple interfaces on the server (Datanode) side.= Clients should also be able to utilize multiple *local* interfaces for out= bound connections instead of always using the interface for the local hostn= ame. This can be accomplished with a new configuration parameter ({{dfs.cli= ent.local.interfaces}}) that accepts a list of interfaces the client should= use. Acceptable configuration values are the same as the {{dfs.datanode.av= ailable.interfaces}} parameter. The client binds its socket to a specific i= nterface, which enables outbound traffic to use that interface. Binding the= client socket to a specific address is not sufficient to ensure egress tra= ffic uses that interface. Eg if multiple interfaces are on the same subnet = the host requires IP rules that use the source address (which bind sets) to= select the destination interface. The SO_BINDTODEVICE socket option could = be used to select a specific interface for the connection instead, however = it requires JNI (is not in Java's SocketOptions) and root access, which we = don't want to require clients have. > Like HDFS-3147, the client can use multiple local interfaces for data tra= nsfer. Since the client already cache their connections to DNs choosing a l= ocal interface at random seems like a good policy. Users can also pin a spe= cific client to a specific interface by specifying just that interface in d= fs.client.local.interfaces. > This change was discussed in HADOOP-6210 a while back, and is actually us= eful/independent of the other HDFS-3140 changes. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrato= rs: https://issues.apache.org/jira/secure/ContactAdministrators!default.jsp= a For more information on JIRA, see: http://www.atlassian.com/software/jira