[
https://issues.apache.org/jira/browse/HADOOP-2551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12556977#action_12556977
]
Allen Wittenauer commented on HADOOP-2551:
------------------------------------------
In particular, I was thinking that it might be useful to have:
HADOOP_GLOBAL_OPTS = applies to all processes
HADOOP_NAMENODE_OPTS = applies to just the namenode
HADOOP_TASK_OPTS = applies to just tasks
HADOOP_JT_OPTS = applies to the job tracker
HADOOP_TT_OPTS = applies to task trackers
HADOOP_CLIENT_OPTS = applies to clients, such as hadoop fsck, hadoop dfs, etc.
Additionally, it might be useful to split out the HADOOP_HEAPSIZE setting as
well.
> 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.
