Return-Path: X-Original-To: apmail-hadoop-hdfs-user-archive@minotaur.apache.org Delivered-To: apmail-hadoop-hdfs-user-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 4045211342 for ; Tue, 20 May 2014 07:43:23 +0000 (UTC) Received: (qmail 59101 invoked by uid 500); 20 May 2014 07:43:19 -0000 Delivered-To: apmail-hadoop-hdfs-user-archive@hadoop.apache.org Received: (qmail 58965 invoked by uid 500); 20 May 2014 07:43:19 -0000 Mailing-List: contact user-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@hadoop.apache.org Delivered-To: mailing list user@hadoop.apache.org Received: (qmail 58958 invoked by uid 99); 20 May 2014 07:43:19 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 20 May 2014 07:43:19 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of rajkrrsingh@gmail.com designates 209.85.216.175 as permitted sender) Received: from [209.85.216.175] (HELO mail-qc0-f175.google.com) (209.85.216.175) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 20 May 2014 07:43:17 +0000 Received: by mail-qc0-f175.google.com with SMTP id w7so127809qcr.34 for ; Tue, 20 May 2014 00:42:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=SMf2jkqSHpVJzePck0YYcOkzQxJtFeulQSqrgL39mYk=; b=B2t13hszg9Q/uFVe6nvDzlzIJbz0xrCmvlCsT3W4rRPxcr3jObH7EQYtmKM/H9Rcwy 7GXQ96vIBsDz+aG2qrjcNDxcoNfLZOzwtIVHTig7fI35E9jO0z5siSiJx1yN8N1tahWa 09jwK68Rg5beS5tw0J4QgK3CjZz9faqYnH0zXcr0+fdw7P4Lcu+Y2/lOZmBflhXtJrkN cmXS8f5ddwlzIGWDhjuPd8oHMWb5zsqTEiVGdHIi8bSx7WVJIjiIFntp3Z3KBW7mylfm b/hgNTh8lcjQ9v9L5y9F+WBaVkiKUJrQU7BdxN/jPkggN+3kgv1GfzQtxqGN0kTFd0h0 HvWw== X-Received: by 10.224.67.201 with SMTP id s9mr1495728qai.29.1400571773645; Tue, 20 May 2014 00:42:53 -0700 (PDT) MIME-Version: 1.0 Received: by 10.140.82.36 with HTTP; Tue, 20 May 2014 00:42:23 -0700 (PDT) In-Reply-To: References: From: Raj K Singh Date: Tue, 20 May 2014 13:12:23 +0530 Message-ID: Subject: Re: Why Hadoop force using DNS? To: user@hadoop.apache.org Content-Type: multipart/alternative; boundary=001a11c303d40cf77704f9d00734 X-Virus-Checked: Checked by ClamAV on apache.org --001a11c303d40cf77704f9d00734 Content-Type: text/plain; charset=UTF-8 Basic Networking practice state using IP addresses is not a very good practice for running production services. Properly administered infrastructure will have working DNS and/or hostname resolution. :::::::::::::::::::::::::::::::::::::::: Raj K Singh http://in.linkedin.com/in/rajkrrsingh http://www.rajkrrsingh.blogspot.com Mobile Tel: +91 (0)9899821370 On Wed, May 14, 2014 at 12:15 PM, tianlijian wrote: > Why Hadoop force using DNS? > --001a11c303d40cf77704f9d00734 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Basic Networking practice state using IP addresses is not = a very good practice for running production services. Properly administered= infrastructure will have working DNS and/or hostname resolution.=C2=A0

:::::::::::::::::::::::::::::::::::::= :::
Raj K Singh
=


On Wed, May 14, 2014 at 12:15 PM, tianli= jian <tianlijian@gmail.com> wrote:
Why Hadoop force using DNS?

--001a11c303d40cf77704f9d00734--