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 "Marco Nicosia (JIRA)" <ji...@apache.org> on 2008/02/02 00:53:10 UTC

[jira] Updated: (HADOOP-2551) hadoop-env.sh needs finer granularity

     [ https://issues.apache.org/jira/browse/HADOOP-2551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marco Nicosia updated HADOOP-2551:
----------------------------------

    Fix Version/s: 0.17.0

Setting Fix Version to Hadoop 0.17. It's important to remember that the hadoop.sh control files are dead stupid, and I don't think we should try to over-engineer them.

> 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
>             Fix For: 0.17.0
>
>
> 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.