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 "Doug Cutting (JIRA)" <ji...@apache.org> on 2006/02/15 23:04:09 UTC
[jira] Resolved: (HADOOP-36) Adding some uniformity/convenience to
environment management
[ http://issues.apache.org/jira/browse/HADOOP-36?page=all ]
Doug Cutting resolved HADOOP-36:
--------------------------------
Resolution: Fixed
I just committed fixes for most of this. The slaves and environment variables are now read from the conf directory. If there are further elements you'd like to see, please submit them as separate bugs.
> Adding some uniformity/convenience to environment management
> ------------------------------------------------------------
>
> Key: HADOOP-36
> URL: http://issues.apache.org/jira/browse/HADOOP-36
> Project: Hadoop
> Type: Improvement
> Components: conf
> Reporter: Bryan Pendleton
>
> Currently, "slaves" are loaded from ~/.slaves. What would be better would be to default from something like conf/hadoop-slaves
> Perhaps split slaves, having a different set for "datanodes" vs. "tasktracker" nodes. ie, conf/hadoop-slaves-tasktracker, conf/hadoop-slaves-datanodes, or some similar split. There's the possibility it's worth building in the assumption that tasktracker is a superset, and thus implicitly includes datanodes, but this might be a bad assumption.
> Also, make sure all scripts source something like conf/hadoop-env.sh. Thus, the user can edit hadoop-env.sh to specify JAVA_HOME, or an alternate HADOOP_SLAVES location. It would also be desirable to have a seed CLASSPATH here. Possibly name it HADOOP_CLASSPATH, to make it explicit and not make hadoop scripts possibly interact with an otherwise-set system CLASSPATH variable.
> These changes would probably be useful to the nutch project, too.
--
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
Re: [jira] Resolved: (HADOOP-36) Adding some uniformity/convenience to environment management
Posted by "Bryan A. Pendleton" <bp...@geekdom.net>.
Looks like good changes. I'm going to have to think about how to add my
"datanodes only" trick in, but this is a great improvement as is. Thanks!
On 2/15/06, Doug Cutting (JIRA) <ji...@apache.org> wrote:
>
> [ http://issues.apache.org/jira/browse/HADOOP-36?page=all ]
>
> Doug Cutting resolved HADOOP-36:
> --------------------------------
>
> Resolution: Fixed
>
> I just committed fixes for most of this. The slaves and environment
> variables are now read from the conf directory. If there are further
> elements you'd like to see, please submit them as separate bugs.
>
> > Adding some uniformity/convenience to environment management
> > ------------------------------------------------------------
> >
> > Key: HADOOP-36
> > URL: http://issues.apache.org/jira/browse/HADOOP-36
> > Project: Hadoop
> > Type: Improvement
> > Components: conf
> > Reporter: Bryan Pendleton
>
> >
> > Currently, "slaves" are loaded from ~/.slaves. What would be better
> would be to default from something like conf/hadoop-slaves
> > Perhaps split slaves, having a different set for "datanodes" vs.
> "tasktracker" nodes. ie, conf/hadoop-slaves-tasktracker,
> conf/hadoop-slaves-datanodes, or some similar split. There's the possibility
> it's worth building in the assumption that tasktracker is a superset, and
> thus implicitly includes datanodes, but this might be a bad assumption.
> > Also, make sure all scripts source something like conf/hadoop-env.sh.
> Thus, the user can edit hadoop-env.sh to specify JAVA_HOME, or an
> alternate HADOOP_SLAVES location. It would also be desirable to have a seed
> CLASSPATH here. Possibly name it HADOOP_CLASSPATH, to make it explicit and
> not make hadoop scripts possibly interact with an otherwise-set system
> CLASSPATH variable.
> > These changes would probably be useful to the nutch project, too.
>
> --
> 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
>
>
--
Bryan A. Pendleton
Ph: (877) geek-1-bp