hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Doug Cutting (JIRA)" <j...@apache.org>
Subject [jira] Closed: (HADOOP-36) Adding some uniformity/convenience to environment management
Date Mon, 24 Apr 2006 23:12:22 GMT
     [ http://issues.apache.org/jira/browse/HADOOP-36?page=all ]
Doug Cutting closed HADOOP-36:

> 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
>      Fix For: 0.1.0

> 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
> 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:
For more information on JIRA, see:

View raw message