Return-Path: Delivered-To: apmail-hadoop-core-user-archive@www.apache.org Received: (qmail 70024 invoked from network); 9 Mar 2009 07:02:15 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 9 Mar 2009 07:02:15 -0000 Received: (qmail 13732 invoked by uid 500); 9 Mar 2009 07:02:09 -0000 Delivered-To: apmail-hadoop-core-user-archive@hadoop.apache.org Received: (qmail 13688 invoked by uid 500); 9 Mar 2009 07:02:09 -0000 Mailing-List: contact core-user-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: core-user@hadoop.apache.org Delivered-To: mailing list core-user@hadoop.apache.org Received: (qmail 13677 invoked by uid 99); 9 Mar 2009 07:02:08 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 09 Mar 2009 00:02:08 -0700 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of rasitozdas@gmail.com designates 209.85.220.157 as permitted sender) Received: from [209.85.220.157] (HELO mail-fx0-f157.google.com) (209.85.220.157) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 09 Mar 2009 07:02:00 +0000 Received: by fxm1 with SMTP id 1so1142218fxm.29 for ; Mon, 09 Mar 2009 00:01:38 -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; bh=/TQgK6Y44+WlcxNXBLoVU1MDH1yTr67pb6c+rpCzglU=; b=LmY9vYDou3TdOeTiaRHJC2iDyUiwI+Rz6C+kqx5JjEgLYXNpJeS4auU/nWO9d78aHZ 1mVB5NZLxbiD8kTaCTmRlAYLMboZGaLlOmern5jRyurqub2SiCk5dvlWEHWlT/e2iKXt ggp8IVoqTgM2IhzGnl219YR7aXuCFmXFYgVv8= 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=BEaEodZLb0yJf0E59hUrSkd7JobtP7d5Hicdcdz0n+XnLwSd+X2Zt+A4gdQkXD0u8w n4EcSUYMJkFPL1R2UiTitImRLdnlE++1Lt6OFxlNY1FtYwNFh0VQcQ1eTvVF+2W02EuA 1b7TU5NB3eXo8nBRhhA5OFdK+sSV+HhHkB8QU= MIME-Version: 1.0 Received: by 10.86.33.10 with SMTP id g10mr3721522fgg.47.1236582098638; Mon, 09 Mar 2009 00:01:38 -0700 (PDT) In-Reply-To: References: Date: Mon, 9 Mar 2009 09:01:38 +0200 Message-ID: Subject: Re: Does "hadoop-default.xml" + "hadoop-site.xml" matter for whole cluster or each node? From: Rasit OZDAS To: core-user@hadoop.apache.org Content-Type: multipart/alternative; boundary=000e0cd24746b998b30464aa3408 X-Virus-Checked: Checked by ClamAV on apache.org --000e0cd24746b998b30464aa3408 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Some parameters are global (I can't give an example now), they are cluster-wide even if they're defined in hadoop-site.xml Rasit 2009/3/9 Nick Cen > for Q1: i think so , but i think it is a good practice to keep the > hadoop-default.xml untouched. > for Q2: i use this property for debugging in eclipse. > > > > 2009/3/9 > > > > > > > The hadoop-site.xml will take effect only on that specified node. So > each > >> node can have its own configuration with hadoop-site.xml. > >> > >> > > As i understand, parameters in "hadoop-site" overwrites these ones in > > "hadoop-default". > > So "hadoop-default" also individual for each node? > > > > Q2: what means "local" as value of "mapred.job.tracker"? > > > > thanks > > > > > > -- > http://daily.appspot.com/food/ > --=20 M. Ra=C5=9Fit =C3=96ZDA=C5=9E --000e0cd24746b998b30464aa3408--