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] Commented: (HADOOP-2551) hadoop-env.sh needs finer granularity
Date Fri, 01 Feb 2008 21:23:08 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-2551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12564939#action_12564939
] 

Doug Cutting commented on HADOOP-2551:
--------------------------------------

Another approach, that also addresses HADOOP-2764, would be to include a hadoop-${COMMAND}-env.sh
if it exists.  So you could add a hadoop-namenode-env.sh that updates various environment
variables to values different from those in the hadoop-env.sh, and, separately, a hadoop-tasktracker-env.sh,
etc.  Could that work?

> hadoop-env.sh needs finer granularity
> -------------------------------------
>
>                 Key: HADOOP-2551
>                 URL: https://issues.apache.org/jira/browse/HADOOP-2551
>             Project: Hadoop Core
>          Issue Type: Improvement
>            Reporter: Allen Wittenauer
>            Priority: Minor
>
> We often configure our HADOOP_OPTS on the name node to have JMX running so that we can
do JVM monitoring.  But doing so means that we need to edit this file if we want to run other
hadoop commands, such as fsck.  It would be useful if hadoop-env.sh was refactored a bit so
that there were different and/or cascading HADOOP_OPTS dependent upon which process/task was
being performed.  

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message