[ http://issues.apache.org/jira/browse/HADOOP-466?page=comments#action_12430174 ] Vetle Roeim commented on HADOOP-466: ------------------------------------
How does _not_ having HADOOP_IDENT_STRING prevent running multiple instances on the same conf dir as different users? The configuration contains port numbers, and the Hadoop daemons won't start if there are already daemons bound to those ports. In any case, running with separate config directories has been greatly simplified with the introduction of the --config command line parameter. > 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
