Return-Path: X-Original-To: apmail-hadoop-hdfs-user-archive@minotaur.apache.org Delivered-To: apmail-hadoop-hdfs-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 392FF119AF for ; Tue, 13 May 2014 09:32:54 +0000 (UTC) Received: (qmail 56988 invoked by uid 500); 13 May 2014 08:30:53 -0000 Delivered-To: apmail-hadoop-hdfs-user-archive@hadoop.apache.org Received: (qmail 56849 invoked by uid 500); 13 May 2014 08:30:53 -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 56842 invoked by uid 99); 13 May 2014 08:30:53 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 13 May 2014 08:30:53 +0000 X-ASF-Spam-Status: No, hits=2.7 required=5.0 tests=FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_REPLY,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of nitinpawar432@gmail.com designates 209.85.213.50 as permitted sender) Received: from [209.85.213.50] (HELO mail-yh0-f50.google.com) (209.85.213.50) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 13 May 2014 08:30:48 +0000 Received: by mail-yh0-f50.google.com with SMTP id 29so5307yhl.23 for ; Tue, 13 May 2014 01:30:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=pr/gKyCDbN2xW/XfJ/xubdkJTpA2wcBLZfUdtyUJE90=; b=XLBXApZr3pNs1NoPqzWMaER7O/6254RDmoZShEuT1Hbgp/Nr34TO8fnn444SFoUo0z 7Mr+BKDdmZnb7OpZwmrpYD19Zn2ghQ1I0gKOlBF+DZGMvo2fnle/fLdYXytJexwnXpZq 8Fw3Gb3dq4+2k3KVxPzHhasJ/8f+53wAVhxjEn9uP/dmDpZvK3QZhehvqtk/Qqt1ojyB evNe3nhI4RIdDHR9YHmKy9ejkLbQuJ9tXqKGun88odhG9zuOOR9dRqqDtDsIqnJ+xjvH IHzHDjw5Dk/lc/SSyc4XD3P3Y/MTkh9FKL5WWW8yFX/WzXXfXQXwaifCmbK53JyHbv6V TxFA== MIME-Version: 1.0 X-Received: by 10.236.130.37 with SMTP id j25mr22349272yhi.106.1399969828302; Tue, 13 May 2014 01:30:28 -0700 (PDT) Received: by 10.170.170.134 with HTTP; Tue, 13 May 2014 01:30:28 -0700 (PDT) In-Reply-To: References: Date: Tue, 13 May 2014 14:00:28 +0530 Message-ID: Subject: Re: Data node with multiple disks From: Nitin Pawar To: user@hadoop.apache.org Content-Type: multipart/alternative; boundary=20cf3011dff54ff41904f943e08f X-Virus-Checked: Checked by ClamAV on apache.org --20cf3011dff54ff41904f943e08f Content-Type: text/plain; charset=UTF-8 Hi Marcos, If these discs are not shared across nodes, I would not worry. Hadoop takes care of making sure data is not replicated to single node. But if all these 20 nodes are sharing these 10 HDD's, Then you may have to basically assign specific disc to specific node and make your cluster rack aware so that the replication in same rack would go to different node and replication to second rack will to new disc. On Tue, May 13, 2014 at 1:38 PM, kishore alajangi wrote: > replication factor=1 > > > On Tue, May 13, 2014 at 11:04 AM, SF Hadoop wrote: > >> Your question is unclear. Please restate and describe what you are >> attempting to do. >> >> Thanks. >> >> >> On Monday, May 12, 2014, Marcos Sousa wrote: >> >>> Hi, >>> >>> I have 20 servers with 10 HD with 400GB SATA. I'd like to use them to be >>> my datanode: >>> >>> /vol1/hadoop/data >>> /vol2/hadoop/data >>> /vol3/hadoop/data >>> /volN/hadoop/data >>> >>> How do user those distinct discs not to replicate? >>> >>> Best regards, >>> >>> -- >>> Marcos Sousa >>> >> > > > -- > Thanks, > Kishore. > -- Nitin Pawar --20cf3011dff54ff41904f943e08f Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi Marcos,
If these discs are not shared across nodes,= I would not worry. Hadoop takes care of making sure data is not replicated= to single node.=C2=A0

But if all these 20 nodes a= re sharing these 10 HDD's,=C2=A0

Then you may have to basically assign specific disc to = specific node and make your cluster rack aware so that the replication in s= ame rack would go to different node and replication to second rack will to = new disc.=C2=A0





On Tue, May 13, 2014 at 1:38 PM, kish= ore alajangi <alajangikishore@gmail.com> wrote:
replication factor=3D1
<= /div>


On Tue, = May 13, 2014 at 11:04 AM, SF Hadoop <sfhadoop@gmail.com> wr= ote:
Your question is unclear. Please restate and= describe what you are attempting to do.

Thanks.=C2=A0


On Monday, May 12, 2014, Marcos Sousa <falecomigo@marcossousa.co= m> wrote:
Hi,

I ha= ve 20 servers with 10 HD with 400GB SATA. I'd like to use them to be my= datanode:=C2=A0

/vol1/hadoop/data
/vol2/hadoop/data
=
/vol3/hadoop/data
/volN/hadoop/data

How do user those= distinct discs not to replicate?

Best regards,

--
Marcos Sousa



--
Thanks,
Kishore.



--
Nitin Pawar<= br>
--20cf3011dff54ff41904f943e08f--