[
https://issues.apache.org/jira/browse/HADOOP-6167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12735846#action_12735846
]
Koji Noguchi commented on HADOOP-6167:
--------------------------------------
bq. how does this not work?
I agree with ryan. It does work as is (at least in our environment).
If the goal is to make it look better, I'm fine.
In our rhel environment, jvm gives preference to latter if argument is provided
twice.
> bin/hadoop script doesn't allow for different memory settings for each daemon
> type
> ----------------------------------------------------------------------------------
>
> Key: HADOOP-6167
> URL: https://issues.apache.org/jira/browse/HADOOP-6167
> Project: Hadoop Common
> Issue Type: Bug
> Affects Versions: 0.20.0
> Reporter: Fernando
> Attachments: hadoop, hadoop-script.diff
>
>
> bin/hadoop assumes that all daemon types ( namenode, datanode, jobtracker,
> tasktracker ), all use the same memory settings.. (HADOOP_HEAPSIZE).
> I propose changes to that script to allow overriding the default memory (
> HADOOP_HEAPSIZE ), with daemon specific OPTS (HADOOP_NAMENODE_OPTS, etc ).
> Basically at the bottom of the bin/hadoop script, it will check to see if the
> user has already set "-Xmx" in the HADOOP_OPTS variable.. if so, then it will
> ignore the JAVA_HEAP_SIZE variable..
> as such:
> # run it
> if [[ $HADOOP_OPTS == *-Xmx* ]]; then
> exec "$JAVA" $HADOOP_OPTS -classpath "$CLASSPATH" $CLASS "$@"
> else
> exec "$JAVA" $JAVA_HEAP_MAX $HADOOP_OPTS -classpath "$CLASSPATH" $CLASS "$@"
> fi
> I will attach the file as I have modified it..
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
