You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Sameer Paranjpye (JIRA)" <ji...@apache.org> on 2006/09/28 22:26:59 UTC
[jira] Updated: (HADOOP-466) Startup scripts will not start
instances of Hadoop daemons w/different configs w/o setting separate PID
directories
[ http://issues.apache.org/jira/browse/HADOOP-466?page=all ]
Sameer Paranjpye updated HADOOP-466:
------------------------------------
Component/s: conf
> 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
> Components: conf
> Affects Versions: 0.5.0
> Reporter: Vetle Roeim
> 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