Return-Path: Delivered-To: apmail-hadoop-common-user-archive@www.apache.org Received: (qmail 73909 invoked from network); 19 Oct 2009 18:47:00 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 19 Oct 2009 18:47:00 -0000 Received: (qmail 53581 invoked by uid 500); 19 Oct 2009 18:46:57 -0000 Delivered-To: apmail-hadoop-common-user-archive@hadoop.apache.org Received: (qmail 53546 invoked by uid 500); 19 Oct 2009 18:46:57 -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 53536 invoked by uid 99); 19 Oct 2009 18:46:57 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 19 Oct 2009 18:46:57 +0000 X-ASF-Spam-Status: No, hits=-2.6 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of edlinuxguru@gmail.com designates 209.85.217.228 as permitted sender) Received: from [209.85.217.228] (HELO mail-gx0-f228.google.com) (209.85.217.228) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 19 Oct 2009 18:46:54 +0000 Received: by gxk28 with SMTP id 28so4123837gxk.9 for ; Mon, 19 Oct 2009 11:46:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=Oxx++orRRo7rO54VYqh3A0I9XaARsYrLSL+vN6HFHMQ=; b=v564PBV+gkhb8O+Iaii2r1WACSqOm8F0q7kI96bXvy4SQI2TkzSrtrFq+GIe61rzfp 4FaHQymq+kKdn8+Df2DaHD2rRAHkcsKxM69RRdyT41olXrArS3FcQ4GNvDbIr6IFeF3V FcyKw+lyjd3JIE4+FGLwolYU/4OcEKwpgHc5w= 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:content-transfer-encoding; b=Lf2S5rkdwo8hg190ecOQU7073RvFzuUa0gLqU5elisqaFSK7wYLQ6nTVoZMsg7HBTC il82+C0WklqnQmoKhqC79W5ErxGm5Y0hEG3SMdf7E/QE4vB43lqsjz23wCVV93trlTBa tAPg5dx0HC6HJMld4v7zZz7L0E9KryJzSg2EQ= MIME-Version: 1.0 Received: by 10.239.139.32 with SMTP id r32mr414358hbr.86.1255977993265; Mon, 19 Oct 2009 11:46:33 -0700 (PDT) In-Reply-To: References: <4ADC6D81.6070204@galatea.com> Date: Mon, 19 Oct 2009 14:46:33 -0400 Message-ID: Subject: Re: editing etc hosts files of a cluster From: Edward Capriolo To: common-user@hadoop.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On Mon, Oct 19, 2009 at 2:36 PM, Allen Wittenauer wrote: > > A bit more specific: > > At Yahoo!, we had either every server as a DNS slave or a DNS caching > server. > > In the case of LinkedIn, we're running Solaris so nscd is significantly > better than its Linux counterpart. =A0However, we still seem to be blowin= g out > the cache too much. =A0So we'll likely switch to DNS caching servers here= as > well. > > On 10/19/09 6:45 AM, "Last-chance Architect" wrot= e: > >> DNS ;) >> >> Ramesh.Ramasamy wrote: >>> Hi, >>> >>> I have a cluster setup with 3 nodes, and I'm adding hostname details (i= n >>> /etc/hosts) manually in each node. Seems it is not an effective approac= h. >>> How this scenario is handled in big clusters? >>> >>> Is there any simple of way to add the hostname details in all the nodes= by >>> editing a single entry/file/script? >>> >>> Thanks and Regards, >>> Ramesh >>> >>> > > Allan, I am interested in your post. What has caused you to run caching DNS servers on each of your nodes? Is this a hadoop specific problem or a problem specific to your implementation? My assumption here is that a hadoop cluster of say 1000 nodes would repeatedly talk to the same 1000 nodes. Are you saying that nscd is inadequacy to handle the size of the cache, or nscd is not very efficient? What exactly is the reason you are running a caching DNS server on each node? Thank you, Edward