Return-Path: X-Original-To: apmail-hadoop-common-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-common-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 427EC96D1 for ; Wed, 11 Apr 2012 04:00:50 +0000 (UTC) Received: (qmail 55550 invoked by uid 500); 11 Apr 2012 04:00:49 -0000 Delivered-To: apmail-hadoop-common-issues-archive@hadoop.apache.org Received: (qmail 55435 invoked by uid 500); 11 Apr 2012 04:00:49 -0000 Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: common-issues@hadoop.apache.org Delivered-To: mailing list common-issues@hadoop.apache.org Received: (qmail 55411 invoked by uid 99); 11 Apr 2012 04:00:48 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 11 Apr 2012 04:00:48 +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; Wed, 11 Apr 2012 04:00:45 +0000 Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116]) by hel.zones.apache.org (Postfix) with ESMTP id 77BF136430D for ; Wed, 11 Apr 2012 04:00:24 +0000 (UTC) Date: Wed, 11 Apr 2012 04:00:24 +0000 (UTC) From: "Eli Collins (Commented) (JIRA)" To: common-issues@hadoop.apache.org Message-ID: <1501736931.10907.1334116824510.JavaMail.tomcat@hel.zones.apache.org> In-Reply-To: <625973047.1326.1332395902366.JavaMail.tomcat@hel.zones.apache.org> Subject: [jira] [Commented] (HADOOP-8198) Support multiple network interfaces MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HADOOP-8198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13251292#comment-13251292 ] Eli Collins commented on HADOOP-8198: ------------------------------------- Use case 2 is the primary motivation,as you point out use case #1 can be addressed purely with host-level bonding. The two scenarios I care most about, that will be used widely, are: # Systems where the on-cluster traffic is on a cluster-private, high-speed (eg infiniband) network, and off-cluster access from clients goes over a separate network. # Systems where the cluster needs a dedicated, high-performance link with an adjacent system (another Hadoop cluster, an EDW, etc) Agree wrt HADOOP-7510, I've been discussing moving tokens off IPs and to hostname or a host-level identifier with Daryn. I think we need to tackle this for HA as well, he's got some good ideas here. > Support multiple network interfaces > ----------------------------------- > > Key: HADOOP-8198 > URL: https://issues.apache.org/jira/browse/HADOOP-8198 > Project: Hadoop Common > Issue Type: New Feature > Components: io, performance > Reporter: Eli Collins > Assignee: Eli Collins > Attachments: MultipleNifsv1.pdf, MultipleNifsv2.pdf, MultipleNifsv3.pdf > > > Hadoop does not currently utilize multiple network interfaces, which is a common user request, and important in enterprise environments. This jira covers a proposal for enhancements to Hadoop so it better utilizes multiple network interfaces. The primary motivation being improved performance, performance isolation, resource utilization and fault tolerance. The attached design doc covers the high-level use cases, requirements, a proposal for trunk/0.23, discussion on related features, and a proposal for Hadoop 1.x that covers a subset of the functionality of the trunk/0.23 proposal. -- 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