Mailing-List: contact hadoop-dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hadoop-dev@lucene.apache.org
Message-ID: <28445400.1156192574837.JavaMail.jira@brutus>
Date: Mon, 21 Aug 2006 13:36:14 -0700 (PDT)
From: "Yoram Arnon (JIRA)" <jira@apache.org>
To: hadoop-dev@lucene.apache.org
Subject: [jira] Commented: (HADOOP-466) Startup scripts will not start
 instances of Hadoop daemons w/different configs w/o setting separate PID
 directories
In-Reply-To: <18080349.1156145293920.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

    [ http://issues.apache.org/jira/browse/HADOOP-466?page=comments#action_12429521 ] 
            
Yoram Arnon commented on HADOOP-466:
------------------------------------

perhaps HADOOP_IDENT_STRING is not required any more, or is indeed harmful.
Having it enables running multiple instances on the same conf dir by running as different users.
it may be ok for log/out files, to separate output from different runs, but for pid files it's better to use the md5 without the string


> Startup scripts will not start instances of Hadoop daemons w/different configs w/o setting separate PID directories
> -------------------------------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-466
>                 URL: http://issues.apache.org/jira/browse/HADOOP-466
>             Project: Hadoop
>          Issue Type: Improvement
>    Affects Versions: 0.5.0
>            Reporter: Vetle Roeim
>             Fix For: 0.6.0
>
>         Attachments: hadoop-466.diff
>
>
> Configuration directories can be specified by either setting HADOOP_CONF_DIR or using the --config command line option. However, the hadoop-daemon.sh script will not start the daemons unless the PID directory is separate for each configuration.
> The issue is that the code for generating PID filenames is not dependent on the configuration directory. While the PID directory can be changed in hadoop-env.sh, it seems a little unnecessary to have this restriction.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira