Mailing-List: contact hdfs-user-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-user@hadoop.apache.org
Received-SPF: pass (athena.apache.org: domain of ajay.bhosle@zapak.co.in
 designates 220.226.181.11 as permitted sender)
Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=default; d=zapak.co.in;
  b=THi6vlidXpTiBMC3iO76Co1w1JYAo5LktqIbG6I+VfH+L5FEGefE3wY79M7d9NOX  ;
From: "ajay.bhosle" <ajay.bhosle@zapak.co.in>
To: <hdfs-user@hadoop.apache.org>
References: <4f3ba093.0336440a.67d6.ffffe1ebSMTPIN_ADDED@mx.google.com>
 <CAOcnVr0-qpbt3A__NFPuieuV+qjfEnuYNhG1aHOG-RW9KZxJNg@mail.gmail.com>
 <CADyz+Ea+yp2diBPQO7VruZco7+61f_zZnCzkO9NPg2kPn_tgdw@mail.gmail.com>
 <4f3defff.c921440a.317f.64fcSMTPIN_ADDED@mx.google.com>
 <CAOcnVr2UH9Lw-ivzpFefrf7raEwgaXZ192q1bXy8gJamMSC61g@mail.gmail.com>
In-Reply-To: 
 <CAOcnVr2UH9Lw-ivzpFefrf7raEwgaXZ192q1bXy8gJamMSC61g@mail.gmail.com>
Subject: RE: Replication
Date: Mon, 20 Feb 2012 11:34:23 +0530
Message-ID: <004a01ccef95$7e45f020$7ad1d060$@bhosle@zapak.co.in>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
thread-index: AcztP0yORy3dvuPnSj6eAqJKY3eCKQCVgE4g
Content-Language: en-us

Harsh,

That was the issue. Thanks a lot.

Ajay

-----Original Message-----
From: Harsh J [mailto:harsh@cloudera.com]=20
Sent: Friday, February 17, 2012 12:11 PM
To: hdfs-user@hadoop.apache.org
Subject: Re: Replication

Ajay,

Some of your client programs are creating files with replication
factor 3 explicitly (or are using a default configuration instead of
your configuration, which sets it to 3). The dfs.replication factor
config isn't cluster-wide as I mentioned before, and a client may
override it (or override via a direct integer value via the Java API)
at will. You need to fix this from the client side.

On Fri, Feb 17, 2012 at 11:42 AM, ajay.bhosle <ajay.bhosle@zapak.co.in>
wrote:
> Hi Denny/Harsh,
>
>
>
> Apart from the below configuration mentioned by me, I also ran the =
setrep
> command to set the replication for existing files. But after some days
when
> I get the block location report it again has a long list of errors
> mentioning =93Target Replicas is 3 but > found 2 replica(s).=94 .
>
>
>
> Thanks
>
> Ajay
>
>
>
> From: Denny Ye [mailto:dennyy99@gmail.com]
> Sent: Friday, February 17, 2012 8:10 AM
> To: hdfs-user@hadoop.apache.org
> Subject: Re: Replication
>
>
>
> hi Ajay
>
> =A0 =A0 Does the file that related with that
> blockId(blk_4884628009930930282_210741) has being=A0existed at HDFS?
>
> =A0 =A0 Your setting is right for new file to HDFS after the =
configuration to
> take effect.
>
>
>
> -Regards
>
> Denny Ye
>
>
>
> 2012/2/15 Harsh J <harsh@cloudera.com>
>
> Ajay,
>
> Replication is a per-file property.
>
> To lower replication factor of existing files, run (as an HDFS
> superuser, for a good measure):
> $ hadoop fs -setrep -R 3 /
>
>
> On Wed, Feb 15, 2012 at 5:39 PM, ajay.bhosle <ajay.bhosle@zapak.co.in>
> wrote:
>> Hi,
>>
>>
>>
>> I have set replication as 1 in hdfs-site.xml as given below,
>>
>>
>>
>> property>
>>
>> =A0=A0=A0 <name>dfs.replication</name>
>>
>> =A0=A0=A0 <value>1</value>
>>
>> =A0=A0=A0 <description>Default block replication.
>>
>> =A0=A0=A0=A0=A0=A0 The actual number of replications can be specified =
when the file
is
>> created.
>>
>> =A0=A0=A0=A0=A0=A0 The default is used if replication is not =
specified in create
time.
>>
>> =A0=A0=A0 </description>
>>
>> =A0</property>
>>
>>
>>
>> But I get the below errors when I retrieve the block report from =
hdfs.
Can
>> someone please help me if I am missing anything.
>>
>>
>>
>> =93Under replicated blk_4884628009930930282_210741. Target Replicas =
is 3
but
>> found 2 replica(s).=94
>>
>>
>>
>> Thanks
>>
>> Ajay
>>
>>
>
>
> --
> Harsh J
> Customer Ops. Engineer
> Cloudera | http://tiny.cloudera.com/about
>
>


--=20
Harsh J
Customer Ops. Engineer
Cloudera | http://tiny.cloudera.com/about