From hdfs-dev-return-2137-apmail-hadoop-hdfs-dev-archive=hadoop.apache.org@hadoop.apache.org Wed Jan 26 02:08:42 2011 Return-Path: Delivered-To: apmail-hadoop-hdfs-dev-archive@minotaur.apache.org Received: (qmail 10783 invoked from network); 26 Jan 2011 02:08:42 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 26 Jan 2011 02:08:42 -0000 Received: (qmail 71296 invoked by uid 500); 26 Jan 2011 02:08:41 -0000 Delivered-To: apmail-hadoop-hdfs-dev-archive@hadoop.apache.org Received: (qmail 71216 invoked by uid 500); 26 Jan 2011 02:08:41 -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 71208 invoked by uid 99); 26 Jan 2011 02:08:41 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 26 Jan 2011 02:08:41 +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 (nike.apache.org: domain of mac.hadoop@gmail.com designates 209.85.218.48 as permitted sender) Received: from [209.85.218.48] (HELO mail-yi0-f48.google.com) (209.85.218.48) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 26 Jan 2011 02:08:33 +0000 Received: by yib17 with SMTP id 17so2122701yib.35 for ; Tue, 25 Jan 2011 18:08:12 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to :content-type; bh=EQUFfB0wJSqzSncGnIBd+Hg60IERXh4h9VcYbnHJm0s=; b=G97Mm0D1Y2NjBivJKChRnk5g1IY726kb1pepXE9Ysrfv1e6B6QWzT+puR4Wv7SQsrk CK8GhofteoqBbcxYkStZLch84zuQY7AOSf96CCl+77HhKrgk/+EhO/9STZRa+ZKoOx5a NVInbjg9vKkM+UBpya7eapdxrJtNf+Qn72nWY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=omvwZIes6QC/jeMPQlAac4vpzzWeOcyXmaXxZpL+Zlj+ff78PGZhv+FoiG3tC/ElVv 2zyuQN600Cvqmqf5xh+U95N2+cW0J/YVGgqVGQnsdp3w7IP0Y3EHlnK0VMDl1sZHr9HT cAvsPogve+4glzj36Agahrzl5/+zgg11OBSVQ= MIME-Version: 1.0 Received: by 10.147.170.7 with SMTP id x7mr8932487yao.23.1296007692788; Tue, 25 Jan 2011 18:08:12 -0800 (PST) Received: by 10.146.167.10 with HTTP; Tue, 25 Jan 2011 18:08:12 -0800 (PST) Date: Wed, 26 Jan 2011 10:08:12 +0800 Message-ID: Subject: Use VIP for DataNodes From: mac fang To: hdfs-dev@hadoop.apache.org Content-Type: multipart/alternative; boundary=20cf3056425527a51b049ab64e3d X-Virus-Checked: Checked by ClamAV on apache.org --20cf3056425527a51b049ab64e3d Content-Type: text/plain; charset=ISO-8859-1 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 --20cf3056425527a51b049ab64e3d--