[
https://issues.apache.org/jira/browse/HADOOP-2551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Raghu Angadi updated HADOOP-2551:
---------------------------------
Release Note: New environment variables were introduced to allow finer
grained control of Java options passed to server and client JVMs. See the new
*_OPTS variables in conf/hadoop-env.sh. (was: hadoop-env.sh supports more
shell variables for finer control of command line options while launching
various services like NameNode, JobTracker, DataNode.)
Nigel's release note is better.
> hadoop-env.sh needs finer granularity
> -------------------------------------
>
> Key: HADOOP-2551
> URL: https://issues.apache.org/jira/browse/HADOOP-2551
> Project: Hadoop Core
> Issue Type: Improvement
> Components: scripts
> Reporter: Allen Wittenauer
> Assignee: Raghu Angadi
> Priority: Blocker
> Fix For: 0.17.0
>
> Attachments: HADOOP-2551.patch
>
>
> 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.
