[
https://issues.apache.org/jira/browse/HADOOP-2551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12556986#action_12556986
]
Doug Cutting commented on HADOOP-2551:
--------------------------------------
I don't think we need HADOOP_GLOBAL_OPTS, we can just use HADOOP_OPTS for that,
but we could add a HADOOP_NAMENODE_OPTS that, when starting the namenode, is
appended to HADOOP_OPTS, etc. In general, we could modify bin/hadoop to add
the value of HADOOP_{$COMMAND}_OPTS to HADOOP_OPTS. Would that suffice?
> hadoop-env.sh needs finer granularity
> -------------------------------------
>
> Key: HADOOP-2551
> URL: https://issues.apache.org/jira/browse/HADOOP-2551
> Project: Hadoop
> 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.
