Return-Path: Delivered-To: apmail-hadoop-common-user-archive@www.apache.org Received: (qmail 94348 invoked from network); 1 Jun 2010 11:49:28 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 1 Jun 2010 11:49:28 -0000 Received: (qmail 2679 invoked by uid 500); 1 Jun 2010 11:49:22 -0000 Delivered-To: apmail-hadoop-common-user-archive@hadoop.apache.org Received: (qmail 2530 invoked by uid 500); 1 Jun 2010 11:49:22 -0000 Mailing-List: contact common-user-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: common-user@hadoop.apache.org Delivered-To: mailing list common-user@hadoop.apache.org Received: (qmail 2504 invoked by uid 99); 1 Jun 2010 11:49:20 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 01 Jun 2010 11:49:20 +0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of jzillmann@googlemail.com designates 74.125.78.26 as permitted sender) Received: from [74.125.78.26] (HELO ey-out-2122.google.com) (74.125.78.26) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 01 Jun 2010 11:49:13 +0000 Received: by ey-out-2122.google.com with SMTP id 4so223644eyf.23 for ; Tue, 01 Jun 2010 04:48:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:received:received:subject:mime-version :content-type:from:in-reply-to:date:cc:content-transfer-encoding :message-id:references:to:x-mailer; bh=+uHnioUtqZhCKjgfbt4mz4Pn5nYleOk9Zt+l8vDIgLg=; b=fjtMWsQ0RUxNV4Zp1uaiDc5ye5MsnKnHE5nySI/gHE4gjYwDGfkXG0w1Nn1EKjt1Vl mzxZy/sYXBBzgtXxG8NdaG+YbI91JNY/QZQyYps75wOacZ3Siq0bFw4wGptfv8hz/KfS lrSjsDIZPtwpw8d8gcr+uSioC11cHiGozP46c= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; b=E5jV395F7hrLyryYSmiaN+V92Hj/SDug3ONZb6bAVbXpuJ49/GrScJfANEnqzdWFT9 pHUp3OmI4HZNzr4x14Tdl4Yx9NxYPyvPZdJWgfBSnfTC3Dd5wROHkASbpgPiaWJjf79T hConDg959Gjxi6BNRkgWOYgNgdaFcJ7jNyurM= Received: by 10.213.29.3 with SMTP id o3mr3256755ebc.59.1275392933253; Tue, 01 Jun 2010 04:48:53 -0700 (PDT) Received: from 83-221-81-89.dynamic.primacom.net (83-221-81-89.dynamic.primacom.net [83.221.81.89]) by mx.google.com with ESMTPS id 14sm3769452ewy.2.2010.06.01.04.48.52 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 01 Jun 2010 04:48:52 -0700 (PDT) Subject: Re: DNS.reverseDns() fallback Mime-Version: 1.0 (Apple Message framework v1078) Content-Type: text/plain; charset=us-ascii From: Johannes Zillmann In-Reply-To: Date: Tue, 1 Jun 2010 13:48:50 +0200 Cc: Content-Transfer-Encoding: quoted-printable Message-Id: <0E3DC199-47C8-40BA-8DD0-A8A1598FE9DB@googlemail.com> References: <54D4320E-7CA6-439E-93F0-9E99E7A91A26@googlemail.com>,, To: common-user@hadoop.apache.org X-Mailer: Apple Mail (2.1078) X-Virus-Checked: Checked by ClamAV on apache.org Thanks for your input! I added an issue for improving the fallback mechanism: = https://issues.apache.org/jira/browse/HADOOP-6797 Johannes On May 28, 2010, at 7:46 PM, Michael Segel wrote: >=20 >=20 >=20 >> Date: Fri, 28 May 2010 13:13:56 -0400 >> Subject: Re: DNS.reverseDns() fallback >> From: esammer@cloudera.com >> To: common-user@hadoop.apache.org >> CC: core-user@hadoop.apache.org > [SNIP] >>> IMHO, after looking at this issue, it really doesn't matter since = the cloud shouldn't be getting a lot of external traffic except on the = name node/job tracker nodes which could be multi-homed. >>=20 >> It might be useful in the case where you're streaming data off of = HDFS >> directly to clients rather than in the MR or HBase case. Data import = / >> export comes to mind. Remember that clients establish a direct >> connection to data nodes so a multihomed NN is insufficient. In that >> case, "external" doesn't necessarily mean a public (routable) IP, but >> simply another network. We've seen use cases for this in some >> installations. One example is a data aggregation or ingestion network >> is separate from the Hadoop internal network and you'd like to get >> data into HDFS. >>=20 >=20 > Eric, > I don't disagree that it is useful.=20 >=20 > I was just offering up an alternative cloud design which would work as = a work-around. > As you point out, clients need to talk to all of the nodes. > So you can make your name node your gateway for the rest of the cloud. > (not a great idea but it works.) > Or you can launch your jobs from a client or clients, who are = multi-homed. >=20 > If you're a Cloudera fan, you could use the cloudera desktop to launch = jobs. > So as long as that machine is visible to the cloud, you'll be OK too. = ;-) >=20 > I don't really recommend this, but its still a viable solution. >=20 > -Mike >=20 >=20 > =20 > _________________________________________________________________ > Hotmail is redefining busy with tools for the New Busy. Get more from = your inbox. > = http://www.windowslive.com/campaign/thenewbusy?ocid=3DPID28326::T:WLMTAGL:= ON:WL:en-US:WM_HMP:042010_2