Return-Path: X-Original-To: apmail-hadoop-general-archive@minotaur.apache.org Delivered-To: apmail-hadoop-general-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 6F6CC43C2 for ; Fri, 13 May 2011 09:57:13 +0000 (UTC) Received: (qmail 25877 invoked by uid 500); 13 May 2011 09:57:11 -0000 Delivered-To: apmail-hadoop-general-archive@hadoop.apache.org Received: (qmail 25818 invoked by uid 500); 13 May 2011 09:57:11 -0000 Mailing-List: contact general-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: general@hadoop.apache.org Delivered-To: mailing list general@hadoop.apache.org Received: (qmail 25810 invoked by uid 99); 13 May 2011 09:57:11 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 13 May 2011 09:57:11 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [145.100.8.49] (HELO smtp.sara.nl) (145.100.8.49) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 13 May 2011 09:57:04 +0000 Received: from planck.ka.sara.nl (145.100.8.32) by sara-exch-fe1.ka.sara.nl (145.100.8.49) with Microsoft SMTP Server (TLS) id 14.0.702.0; Fri, 13 May 2011 11:56:42 +0200 Received: from planck.ka.sara.nl ([145.100.8.32]) by planck.ka.sara.nl ([145.100.8.32]) with mapi; Fri, 13 May 2011 11:56:42 +0200 From: Evert Lammerts To: "" , "" Date: Fri, 13 May 2011 11:54:40 +0200 Subject: RE: Stability issue - dead DN's Thread-Topic: Stability issue - dead DN's Thread-Index: AcwQANbHLbwnC3EHT6WAQGeZF8GBhABUUebQ Message-ID: References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Hi Mike, > You really really don't want to do this. > Long story short... It won't work. Can you elaborate? Are you talking about the bonded interfaces or about hav= ing a separated network for interconnects and external network? What can go= wrong there? > > Just a suggestion.. You don't want anyone on your cluster itself. They > should interact wit edge nodes, which are 'Hadoop aware'. Then your > cluster has a single network to worry about. That's our current setup. We have a single headnode that is used as a SPOE.= However, I'd like to change that on our future production system. We want = to implement Kerberos for authentication, and let users interact with the c= luster from their own machine. This would enable them to submit their jobs = from the local IDE. The only way to do this is by opening up Hadoop ports f= or the world, is my understanding: if people interact with HDFS they need t= o be able to interact with all nodes, right? What would be the argument aga= inst this? Cheers, Evert > > > Sent from a remote device. Please excuse any typos... > > Mike Segel > > On May 11, 2011, at 11:45 AM, Allen Wittenauer wrote: > > > > > > > > > > >>> * a 2x1GE bonded network interface for interconnects > >>> * a 2x1GE bonded network interface for external access > > > > Multiple NICs on a box can sometimes cause big performance > problems with Hadoop. So watch your traffic carefully. > > > > > >