[
https://issues.apache.org/jira/browse/HADOOP-2551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12595992#action_12595992
]
Vinod Kumar Vavilapalli commented on HADOOP-2551:
-------------------------------------------------
What happened with the idea of doing away with HADOOP_HEAPSIZE completely? The
patch doesn't have any fix for this. Track this on another JIRA?
Currently, if I specify both HADOOP_HEAPSIZE=500 and
HADOOP_JOBTRACKER_OPTS=-Xmx1024m, both get passed to jobtracker (JT command
line: "java -Xmx500m -Xmx1024m .......") and the runtime picks up the last
value. So, it works for now, but it would have been cleaner had HADOOP_HEAPSIZE
been kicked of in entirety.
> 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.
