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 5727310412 for ; Sun, 8 Dec 2013 22:29:06 +0000 (UTC) Received: (qmail 45920 invoked by uid 500); 8 Dec 2013 22:29:01 -0000 Delivered-To: apmail-hadoop-mapreduce-user-archive@hadoop.apache.org Received: (qmail 45770 invoked by uid 500); 8 Dec 2013 22:29:01 -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 45763 invoked by uid 99); 8 Dec 2013 22:29:01 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 08 Dec 2013 22:29:01 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of forrie@gmail.com designates 209.85.128.47 as permitted sender) Received: from [209.85.128.47] (HELO mail-qe0-f47.google.com) (209.85.128.47) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 08 Dec 2013 22:28:54 +0000 Received: by mail-qe0-f47.google.com with SMTP id t7so2286506qeb.34 for ; Sun, 08 Dec 2013 14:28:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type; bh=/nvfckZGTWVXzN6gNhtnzC0ab7Rd3H/afdYErigDUoU=; b=xP5ZqesRQk2pxiZrBESGzFQbxldjncJwoGWIIMDAoSJBZzkOKuaGbIclDKvBp47vzW DABzdEWWQm17vSeA/h5huQnB8GpxRsXsQzJVNvjT+6DrL5hYEjNg9bepJ2JrnvbpEMQp otMa83Q8A5Y+qfkLhyCu3WaOJ6mn8zjC2ebMUj8lVEtuucWCBX7Hzr8CsVzwYlFd5FRE ui9UR/jpbY4Z1R9dpnj2WxmYEwT6Z1c+oazOgo5okti0abbTNSBhCZbkYAxMM8wfwKjq aVPBBcKVXZ2dr912+T7Wv0HR+nPbrFtiCWaH9jdCIahMJVsnDsoSoayxtChI0zrczsfM nT8Q== X-Received: by 10.49.132.65 with SMTP id os1mr162156146qeb.39.1386541713918; Sun, 08 Dec 2013 14:28:33 -0800 (PST) Received: from hiram-6.local (c-24-218-93-202.hsd1.nh.comcast.net. [24.218.93.202]) by mx.google.com with ESMTPSA id nq5sm22815787qeb.8.2013.12.08.14.28.33 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 08 Dec 2013 14:28:33 -0800 (PST) Message-ID: <52A4F28E.1010706@gmail.com> Date: Sun, 08 Dec 2013 17:28:30 -0500 From: Forrest Aldrich User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.1.1 MIME-Version: 1.0 To: user@hadoop.apache.org Subject: Re: Setting the HADOOP_HOME_DIR References: <52A4C683.6010602@gmail.com> In-Reply-To: Content-Type: multipart/alternative; boundary="------------080307070603030403060502" X-Virus-Checked: Checked by ClamAV on apache.org This is a multi-part message in MIME format. --------------080307070603030403060502 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Adam, my apologies, you are correct. I meant to refer to the HADOOP_CONF_DIR -- this is what I get for posting before I've had enough coffee :-) I want to put the CONF and LOGS directories outside of the /usr/hadoop structure -- this will make it easier to manage with Puppet, and prevent accidental overwrites during upgrades etc. Thanks. On 12/8/13, 4:56 PM, Adam Kawa wrote: > Hi, > > If am not sure, if I understood your issue correctly. Would you like > to specify somehow where the configuration directory for your Hadoop > cluster is located (e.g. /etc/hadoop/conf)? > > If you use init scripts from CDH, they assume that config directory is > CONF_DIR="/etc/hadoop/conf". > Afaik, when you use HDP or Apache distribution, then you can specify > where your configuration directory is when you start a script e.g. > "sudo -u hdfs /usr/lib/hadoop/sbin/hadoop-daemon.sh --config > start datanode" > > PS. > I grepped my configuration directory, and installation directory > (/usr/lib/hadoop), but I can not see variable called: HADOOP_HOME_DIR > anywhere. > I see that /usr/lib/hadoop/libexec/hadoop-layout.sh contains variable > HADOOP_CONF_DIR=${HADOOP_CONF_DIR:-"/etc/hadoop/conf"}. > > > 2013/12/8 Forrest Aldrich > > > We have a home-grown Hadoop installation that I am primarily > responsible for. I've managed to get new nodes rolled out, it > takes time as we have other dependencies. One item I've not been > able figure out is where to set the HADOOP_HOME_DIR variable, so I > can store the actual configuration for each node separate from the > binary tree. > > Can anyone point me to where this gets set properly? We have an > init.d script that starts the services on the master, which calls > out to the slaves (as user "hadoop") -- but I'm guessing the > variable can be started there, exported and inherited -- but > perhaps it may be more proper to set in ~hadoop/conf/hadoop-env.sh. > > The idea is to enable me to more easily roll out slaves, perhaps > using Puppet, so that the CONF and LOGS directories are separate > -- it's easier to manage that way. > > > Thanks. > > --------------080307070603030403060502 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Adam, my apologies, you are correct.  I meant to refer to the HADOOP_CONF_DIR -- this is what I get for posting before I've had enough coffee :-)

I want to put the CONF and LOGS directories outside of the /usr/hadoop structure -- this will make it easier to manage with Puppet, and prevent accidental overwrites during upgrades etc.


Thanks.


On 12/8/13, 4:56 PM, Adam Kawa wrote:
Hi,

If am not sure, if I understood your issue correctly. Would you like to specify somehow where the configuration directory for your Hadoop cluster is located (e.g. /etc/hadoop/conf)?

If you use init scripts from CDH, they assume that config directory is CONF_DIR="/etc/hadoop/conf".
Afaik, when you use HDP or Apache distribution, then you can specify where your configuration directory is when you start a script e.g. "sudo -u hdfs /usr/lib/hadoop/sbin/hadoop-daemon.sh --config <config_directory> start datanode"

PS.
I grepped my configuration directory, and installation directory (/usr/lib/hadoop), but I can not see variable called: HADOOP_HOME_DIR anywhere.
I see that /usr/lib/hadoop/libexec/hadoop-layout.sh contains variable HADOOP_CONF_DIR=${HADOOP_CONF_DIR:-"/etc/hadoop/conf"}.


2013/12/8 Forrest Aldrich <forrie@gmail.com>
We have a home-grown Hadoop installation that I am primarily responsible for.   I've managed to get new nodes rolled out, it takes time as we have other dependencies.   One item I've not been able figure out is where to set the HADOOP_HOME_DIR variable, so I can store the actual configuration for each node separate from the binary tree.

Can anyone point me to where this gets set properly?   We have an init.d script that starts the services on the master, which calls out to the slaves (as user "hadoop") -- but I'm guessing the variable can be started there, exported and inherited -- but perhaps it may be more proper to set in ~hadoop/conf/hadoop-env.sh.

The idea is to enable me to more easily roll out slaves, perhaps using Puppet, so that the CONF and LOGS directories are separate -- it's easier to manage that way.


Thanks.



--------------080307070603030403060502--