Return-Path: X-Original-To: apmail-hadoop-user-archive@minotaur.apache.org Delivered-To: apmail-hadoop-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 8E82DD022 for ; Thu, 7 Mar 2013 16:31:01 +0000 (UTC) Received: (qmail 86957 invoked by uid 500); 7 Mar 2013 16:30:56 -0000 Delivered-To: apmail-hadoop-user-archive@hadoop.apache.org Received: (qmail 86650 invoked by uid 500); 7 Mar 2013 16:30:56 -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 86621 invoked by uid 99); 7 Mar 2013 16:30:55 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 07 Mar 2013 16:30:55 +0000 X-ASF-Spam-Status: No, hits=3.2 required=5.0 tests=FREEMAIL_REPLY,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS,T_REMOTE_IMAGE X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of j_mezazap@hotmail.com designates 65.55.111.93 as permitted sender) Received: from [65.55.111.93] (HELO blu0-omc2-s18.blu0.hotmail.com) (65.55.111.93) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 07 Mar 2013 16:30:48 +0000 Received: from BLU002-W66 ([65.55.111.71]) by blu0-omc2-s18.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Thu, 7 Mar 2013 08:30:28 -0800 X-EIP: [3Ln/woeiebf0ka7WHM9Uw/0shVYFb0sA] X-Originating-Email: [j_mezazap@hotmail.com] Message-ID: Content-Type: multipart/alternative; boundary="_7a379ee4-62cb-42d4-8bf3-f7c03e444960_" From: John Meza To: "user@hadoop.apache.org" Subject: RE: dfs.datanode.du.reserved Date: Thu, 7 Mar 2013 08:30:27 -0800 Importance: Normal In-Reply-To: References: , ,, MIME-Version: 1.0 X-OriginalArrivalTime: 07 Mar 2013 16:30:28.0543 (UTC) FILETIME=[1431C4F0:01CE1B51] X-Virus-Checked: Checked by ClamAV on apache.org --_7a379ee4-62cb-42d4-8bf3-f7c03e444960_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Ok. I'll add my ideas and comments. From: harsh@cloudera.com Date: Thu=2C 7 Mar 2013 06:37:20 +0530 Subject: Re: dfs.datanode.du.reserved To: user@hadoop.apache.org Hey John=2C Ideas=2C comments and patches are welcome on https://issues.apache.org/jira= /browse/HDFS-1564 for achieving this!=0A= =0A= On Wed=2C Mar 6=2C 2013 at 9:56 PM=2C John Meza wro= te: =0A= =0A= =0A= =0A= =0A= Thanks for the reply. This sounds like it has potential=2C but also seems t= o be a rather duct-tape type of work around. It would be nice if there was = a mod to dfs.datanode.du.reserved that worked within Hadoop=2C so that woul= d imply that hadoop was a little more certain to adhere to it. =0A= =0A= I understand that dfs.datanode.du.reserved defines reservd storage on each = volume. I would like to give each volume a different reserved value. An example: dfs.datanode.du.reserved=0A= ///hstore1/dfs/dn:161061273600=2C///hstore2/dfs/dn:53687091200=0A= =0A= Or something similiar. thanks=20 John Date: Wed=2C 6 Mar 2013 10:25:17 +0100 Subject: Re: dfs.datanode.du.reserved From: dechouxb@gmail.com =0A= =0A= To: user@hadoop.apache.org Not that I know. If so you should be able to identify each volume and as of= now this isn't the case. =0A= =0A= BUT it can be done without Hadoop knowing about it=2C at the OS level=2C us= ing different partitions/mounts for datanode and jobtracker stuff. That sho= uld solve your problem. =0A= Regards Bertrand On Mon=2C Mar 4=2C 2013 at 10:26 PM=2C John Meza wr= ote: =0A= =0A= =0A= =0A= I'm probably not being clear.this seems to describe it: dfs.datanode.du.res= erved configured per-volume.=0A= =0A= =0A= https://issues.apache.org/jira/browse/HDFS-1564 =0A= =0A= =0A= thanksJohn From: outlawdba@gmail.com Date: Mon=2C 4 Mar 2013 15:37:36 -0500 Subject: Re: dfs.datanode.du.reserved To: user@hadoop.apache.org=0A= =0A= =0A= Possible to reserve 0 from various testing I have done yet that could cause= the obvious side effect of achieving zero disk space:) Have only tested in= development environment=2C however. Yet there are various tuning white pap= ers and other benchmarks where the very same has been tested.=20 =0A= =0A= =0A= =0A= =0A= Thanks.=20 On Mon=2C Mar 4=2C 2013 at 2:00 PM=2C John Meza wro= te: =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= the parameter: dfs.datanode.du.reserved is used to reserve disk space PER d= atanode. Is it possible to reserve a different amount of disk space per DIS= K?=0A= =0A= =0A= =0A= =0A= thanks=0A= =0A= =0A= =0A= =0A= John =0A= =0A= =0A= =0A= =0A= =0A= --=20 Ellis R. Miller937.829.2380 =0A= =0A= =0A= Mundo Nulla Fides =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= --=20 Harsh J=0A= = --_7a379ee4-62cb-42d4-8bf3-f7c03e444960_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Ok. I'll add my ideas and commen= ts.


From: harsh@cloudera.com
Date: Thu=2C 7 Mar 2013 06:37:20 +0530
Su= bject: Re: dfs.datanode.du.reserved
To: user@hadoop.apache.org

Hey John=2C

Ideas=2C comments and patches= are welcome on =3Bhttps://issues.apache.org/jira/browse/HDFS-1564 =3Bfor achieving this!
=0A= =0A=


O= n Wed=2C Mar 6=2C 2013 at 9:56 PM=2C John Meza <=3Bj_mezazap@hotmail.co= m>=3B wrote:
=0A= =0A=
=0A= =0A= =0A=
Thanks for the reply. This sounds like it has potenti= al=2C but also seems to be a rather duct-tape type of work around. It would= be nice if there was a mod to dfs.datanode.du.reserved that worked within = Hadoop=2C so that would imply that hadoop was a little more certain to adhe= re to it. =3B
=0A= =0A=
I understand that dfs.datanode.du.reserved defines reservd s= torage on each volume. I would like to give each volume a different reserve= d value.

An example:
 <=
=3Bname>=3Bdfs.datanode.du.reserved<=3B/name>=3B=0A=
   <=3Bvalue>=3B///hstore1/dfs/dn:161061273600=2C///hstore2/dfs/dn:53687091200<=3B/value>=3B
=0A= =0A= Or something similiar. =3B
thanks =3B
John

Date: Wed=2C 6 Mar 2013 10:25:17 +0100
Subject: Re: dfs.data= node.du.reserved
From: dechouxb@gmail.com
=0A= =0A= To: user@hadoop= .apache.org


Not that I know. If so you sh= ould be able to identify each volume and as of now this isn't the case.
= =0A= =0A= BUT it can be done without Hadoop knowing about it=2C at the OS level=2C us= ing different partitions/mounts for datanode and jobtracker stuff. That sho= uld solve your problem.
=0A=
Regards

Bertrand

On Mon=2C Mar 4=2C 2013 at 10:26 PM= =2C John Meza <=3Bj_mezazap@hotmail.com>=3B wrote:
=0A=
=0A= =0A= =0A=
I'm probably not being clear.
this seems to descr= ibe it: =3Bdfs.datanode.du.reserved &= nbsp=3Bconfigured per-volume.
=0A= =0A= =0A=
John

From: outlawdba@gmail.com
Date: Mon=2C 4 = Mar 2013 15:37:36 -0500
Subject: Re: dfs.datanode.du.reserved
To: user@hadoop.apache= .org
=0A= =0A= =0A=


Possible to reserve 0 from various testing I have done yet tha= t could cause the obvious side effect of achieving zero disk space:) Have o= nly tested in development environment=2C however. Yet there are various tun= ing white papers and other benchmarks where the very same has been tested. =
=0A= =0A= =0A= =0A= =0A=
Thanks.

On Mon=2C Mar 4=2C 2013 at 2:00 PM=2C John Meza <=3Bj_mezazap@hotmail.com>=3B wrote:
=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A=
the parameter: =3Bdfs.datanod= e.du.reserved is used to reserve disk space PER datanode. Is it possible to reserve a di= fferent amount of disk space per DISK?
=0A= =0A= =0A= =0A= =0A=
thanks
=0A= =0A= =0A= =0A= =0A=
John
=
=0A= =0A= =0A= =0A= =0A=
=0A=



--
=
Ellis R. Miller

=0A=
=0A= =0A=

Mundo Nulla Fides
=0A= =0A=


=0A= =0A= =0A= =0A=
=0A=

=0A=

=0A=



--
Harsh J=0A=
= --_7a379ee4-62cb-42d4-8bf3-f7c03e444960_--