[
https://issues.apache.org/jira/browse/HADOOP-6167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12734692#action_12734692
]
ryan rawson commented on HADOOP-6167:
-------------------------------------
I'm not sure this is true, my datanode processes are running like so:
/usr/java/jdk1.6.0_14/bin/java -Xmx1000m -Dcom.sun.management.jmxremote
-Xmx2000m -XX:+DoEscapeAnalysis (all the other arguments)
in hadoop-env.sh i have:
export HADOOP_DATANODE_OPTS="-Xmx2000m -XX:+DoEscapeAnalysis ...."
how does this not work?
> 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
>
>
> 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.
