Return-Path: Delivered-To: apmail-hadoop-hdfs-dev-archive@minotaur.apache.org Received: (qmail 788 invoked from network); 26 Jan 2011 05:47:31 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 26 Jan 2011 05:47:31 -0000 Received: (qmail 8500 invoked by uid 500); 26 Jan 2011 05:47:31 -0000 Delivered-To: apmail-hadoop-hdfs-dev-archive@hadoop.apache.org Received: (qmail 8138 invoked by uid 500); 26 Jan 2011 05:47:27 -0000 Mailing-List: contact hdfs-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hdfs-dev@hadoop.apache.org Delivered-To: mailing list hdfs-dev@hadoop.apache.org Received: (qmail 8100 invoked by uid 99); 26 Jan 2011 05:47:26 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 26 Jan 2011 05:47:26 +0000 X-ASF-Spam-Status: No, hits=1.5 required=10.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of dhruba@gmail.com designates 74.125.82.42 as permitted sender) Received: from [74.125.82.42] (HELO mail-ww0-f42.google.com) (74.125.82.42) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 26 Jan 2011 05:47:22 +0000 Received: by wwi17 with SMTP id 17so4673379wwi.5 for ; Tue, 25 Jan 2011 21:47:01 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=oFI+kpABP6FEGfwLludA1RM6nhW68AzyXFyTIFrcLag=; b=ex6OQ9IeTGd4RktMtZKPpytC3Kd51P++LirUdQGGgPobJgCXHZe3ATIqlG5o4bSIfW IaqRb5KGuEMTwdpd53gWMZyMkIlI/gXHCbhztL36ShvRZW/QqeQsIktIOLpsQownsNRQ 9SUuu1FbCFPjVNY8KYhS9Hu+ArohPQlLZTJdM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=My+La3WYEbe/RNWp9BTCpLViUsNHVIF0kYK4yHkUMs6h+4bxS8MuqT10rDHR+dGosQ L31pMXsq45tWivI+rgjxsNrS/U+bbtZWCB031BQPFcF8jjYx9gWC0zCUMwdGcVCHIZpR FF4UAJT4JZ6Nsy2+NnXFoklT3sxopgqjk5UEo= MIME-Version: 1.0 Received: by 10.216.179.144 with SMTP id h16mr676767wem.64.1296020820621; Tue, 25 Jan 2011 21:47:00 -0800 (PST) Received: by 10.216.159.5 with HTTP; Tue, 25 Jan 2011 21:47:00 -0800 (PST) In-Reply-To: References: Date: Tue, 25 Jan 2011 21:47:00 -0800 Message-ID: Subject: Re: Use VIP for DataNodes From: Dhruba Borthakur To: hdfs-dev@hadoop.apache.org Content-Type: multipart/alternative; boundary=0016e64c1e76a27912049ab95cee --0016e64c1e76a27912049ab95cee Content-Type: text/plain; charset=ISO-8859-1 Fb does not use the VIP approach, we tried that but quickly found out some limitations, one main problem being that the failover server pair has to be in the same subnet (for VIP to work). Instead we now use the AvatarNode integrated with Zookeeper. -dhruba On Tue, Jan 25, 2011 at 6:12 PM, Harsh J wrote: > This is a good approach, is used by many to mask the NameNode address > for the DataNodes; and is also good to use while using BackupNode > (Even Facebook does this). > > On Wed, Jan 26, 2011 at 7:38 AM, mac fang wrote: > > Hi, guys, > > > > Do we have any plan to enable VIP between NameNode and DataNodes, I mean > > multiple NameNodes and we use a VIP stands before the NNs. Then DNs only > > need to connect to the VIP. I don't know if it is valuable we have this > impl > > in our hdsf and if there has any issues? > > > > Any hints are valuable for me. :) > > > > regards > > macf > > > > > > -- > Harsh J > www.harshj.com > -- Connect to me at http://www.facebook.com/dhruba --0016e64c1e76a27912049ab95cee--