Return-Path: X-Original-To: apmail-hadoop-mapreduce-user-archive@minotaur.apache.org Delivered-To: apmail-hadoop-mapreduce-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 0EC0CD415 for ; Mon, 15 Oct 2012 19:18:52 +0000 (UTC) Received: (qmail 80376 invoked by uid 500); 15 Oct 2012 19:18:47 -0000 Delivered-To: apmail-hadoop-mapreduce-user-archive@hadoop.apache.org Received: (qmail 80207 invoked by uid 500); 15 Oct 2012 19:18:47 -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 80198 invoked by uid 99); 15 Oct 2012 19:18:47 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 15 Oct 2012 19:18:47 +0000 X-ASF-Spam-Status: No, hits=2.2 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [209.85.215.48] (HELO mail-la0-f48.google.com) (209.85.215.48) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 15 Oct 2012 19:18:41 +0000 Received: by mail-la0-f48.google.com with SMTP id u2so4079845lag.35 for ; Mon, 15 Oct 2012 12:18:19 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:x-gm-message-state; bh=h6fiE2NBIWm40gbdvzDORJKXA7DcP03fuNw7z5wJlVs=; b=l8qKXVHCxRxXTMzNbpx/Dz20R/V0Vc0wDMgB/D2V7G5SSwiOm80t3WxWmP7Kvslvvn 1BZPuma9Z+ZO0L8iBJKwsv/uXI5esuVxnF/tL+F7SAgG2kvQaz5RhPUlR44MQHnrpGpg 5oukz+ZTrPTfqjli6jY6sBzxQyZxo5wj1TFOxhpJXkJtknOhC1DCvhLzyXz/VWl4GyK3 Eb5Tmt2lgHpoTTEeCUK9kZ43GzeJIwCgKE29ZDUu0BDd8CZyz5VH12HAU30ZYiqV0yLN FzfaZ2X6vr74b9Bsk31GjdbKWNhAkiqqZ2YXbnjMhZ3/MjyiPLiZnW16Q42fCyBG/eFw fV4Q== MIME-Version: 1.0 Received: by 10.112.37.226 with SMTP id b2mr744543lbk.129.1350328699158; Mon, 15 Oct 2012 12:18:19 -0700 (PDT) Received: by 10.114.26.6 with HTTP; Mon, 15 Oct 2012 12:18:19 -0700 (PDT) In-Reply-To: References: Date: Mon, 15 Oct 2012 12:18:19 -0700 Message-ID: Subject: Re: final the dfs.replication and fsck From: Chris Nauroth To: user@hadoop.apache.org Content-Type: multipart/alternative; boundary=e0cb4efe2e4c7180ea04cc1de669 X-Gm-Message-State: ALoCoQlrYrx1qu3Ijx/SG1uXlO3p2Q//Tv0IB9qkAQjs43AYWSnINhGvKEx/EqQizf7o8fUJQo7Y X-Virus-Checked: Checked by ClamAV on apache.org --e0cb4efe2e4c7180ea04cc1de669 Content-Type: text/plain; charset=ISO-8859-1 Hello Patai, Has your configuration file change been copied to all nodes in the cluster? Are there applications connecting from outside of the cluster? If so, then those clients could have separate configuration files or code setting dfs.replication (and other configuration properties). These would not be limited by final declarations in the cluster's configuration files. true controls configuration file resource loading, but it does not necessarily block different nodes or different applications from running with completely different configurations. Hope this helps, --Chris On Mon, Oct 15, 2012 at 12:01 PM, Patai Sangbutsarakum < silvianhadoop@gmail.com> wrote: > Hi Hadoopers, > > I have > > dfs.replication > 2 > true > > > set in hdfs-site.xml in staging environment cluster. while the staging > cluster is running the code that will later be deployed in production, > those code is trying to have dfs.replication of 3, 10, 50, other than > 2; the number that developer thought that will fit in production > environment. > > Even though I final the property dfs.replication in staging cluster > already. every time i run fsck on the staging cluster i still see it > said under replication. > I thought final keyword will not honor value in job config, but it > doesn't seem so when i run fsck. > > I am on cdh3u4. > > please suggest. > Patai > --e0cb4efe2e4c7180ea04cc1de669 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hello Patai,

Has your configuration file change been cop= ied to all nodes in the cluster?

Are there applica= tions connecting from outside of the cluster? =A0If so, then those clients = could have separate configuration files or code setting dfs.replication (an= d other configuration properties). =A0These would not be limited by final d= eclarations in the cluster's configuration files. =A0<final>true&= lt;/final> controls configuration file resource loading, but it does not= necessarily block different nodes or different applications from running w= ith completely different configurations.

Hope this helps,
--Chris

On Mon, Oct 15, 2012 at 12:01 PM, Patai Sangbutsarakum <silvianhadoop@gmail.com> wrote:
Hi Hadoopers,

I have
<property>
=A0 =A0 <name>dfs.replication</name>
=A0 =A0 <value>2</value>
=A0 =A0 <final>true</final>
=A0 </property>

set in hdfs-site.xml in staging environment cluster. while the staging
cluster is running the code that will later be deployed in production,
those code is trying to have dfs.replication of 3, 10, 50, other than
2; the number that developer thought that will fit in production
environment.

Even though I final the property dfs.replication in staging cluster
already. every time i run fsck on the staging cluster i still see it
said under replication.
I thought final keyword will not honor value in job config, but it
doesn't seem so when i run fsck.

I am on cdh3u4.

please suggest.
Patai

--e0cb4efe2e4c7180ea04cc1de669--