Return-Path: 
 <hdfs-dev-return-5088-apmail-hadoop-hdfs-dev-archive=hadoop.apache.org@hadoop.apache.org>
X-Original-To: apmail-hadoop-hdfs-dev-archive@minotaur.apache.org
Delivered-To: apmail-hadoop-hdfs-dev-archive@minotaur.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 844C59BDD
	for <apmail-hadoop-hdfs-dev-archive@minotaur.apache.org>;
 Tue, 20 Dec 2011 05:35:42 +0000 (UTC)
Received: (qmail 66545 invoked by uid 500); 20 Dec 2011 05:35:41 -0000
Delivered-To: apmail-hadoop-hdfs-dev-archive@hadoop.apache.org
Received: (qmail 66504 invoked by uid 500); 20 Dec 2011 05:35:41 -0000
Mailing-List: contact hdfs-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:hdfs-dev-help@hadoop.apache.org>
List-Unsubscribe: <mailto:hdfs-dev-unsubscribe@hadoop.apache.org>
List-Post: <mailto:hdfs-dev@hadoop.apache.org>
List-Id: <hdfs-dev.hadoop.apache.org>
Reply-To: hdfs-dev@hadoop.apache.org
Delivered-To: mailing list hdfs-dev@hadoop.apache.org
Received: (qmail 66486 invoked by uid 99); 20 Dec 2011 05:35:39 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 20 Dec 2011 05:35:39 +0000
X-ASF-Spam-Status: No, hits=1.3 required=5.0
	tests=SPF_PASS,URI_HEX
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: domain of harsh@cloudera.com designates
 209.85.213.48 as permitted sender)
Received: from [209.85.213.48] (HELO mail-yw0-f48.google.com) (209.85.213.48)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 20 Dec 2011 05:35:33 +0000
Received: by yhpp56 with SMTP id p56so5088219yhp.35
        for <multiple recipients>; Mon, 19 Dec 2011 21:35:12 -0800 (PST)
Received: by 10.236.145.195 with SMTP id p43mr733430yhj.99.1324359312096;
        Mon, 19 Dec 2011 21:35:12 -0800 (PST)
Received: from [192.168.1.2] ([59.92.58.255])
        by mx.google.com with ESMTPS id 37sm1941483anu.21.2011.12.19.21.35.08
        (version=TLSv1/SSLv3 cipher=OTHER);
        Mon, 19 Dec 2011 21:35:11 -0800 (PST)
Subject: Re: Controlling the placement of data in Hadoop Cluster nodes ?
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Harsh J <harsh@cloudera.com>
In-Reply-To: <1324358963825-3600410.post@n3.nabble.com>
Date: Tue, 20 Dec 2011 11:05:03 +0530
Cc: ArunKumar <arunk786@gmail.com>
Content-Transfer-Encoding: quoted-printable
Message-Id: <41A9AE46-9929-47A2-A13A-75B66CBDEACC@cloudera.com>
References: <1324358963825-3600410.post@n3.nabble.com>
To: hdfs-dev@hadoop.apache.org
X-Mailer: Apple Mail (2.1084)

Moving to hdfs-dev@hadoop.apache.org. In future, please use the =
appropriate lists to post your questions, when they are about HDFS: =
http://hadoop.apache.org/hdfs/mailing_lists.html

You can implement a custom BlockPlacementPolicy in 0.21+ versions of =
Hadoop, and use that to achieve this. Should be fairly straight forward =
to do for test purposes -- just take a look at the interface.

On 20-Dec-2011, at 10:59 AM, ArunKumar wrote:

> Hi guys !
>=20
> I don't want to use automatic placement of HDFS for some reasons.
> Can i control the placement of data in Hadoop Cluster nodes ?
> Say placing data1 on Node3 , data2 on Node5 ,etc
>=20
> Can anyone guide me in this regard ?
>=20
>=20
> Arun
>=20
>=20
> --
> View this message in context: =
http://lucene.472066.n3.nabble.com/Controlling-the-placement-of-data-in-Ha=
doop-Cluster-nodes-tp3600410p3600410.html
> Sent from the Hadoop lucene-users mailing list archive at Nabble.com.