Chen He created AMBARI-15434: -------------------------------- Summary: Ambari set too small -Xmx value in default when create a cluster from blueprint Key: AMBARI-15434 URL: https://issues.apache.org/jira/browse/AMBARI-15434 Project: Ambari Issue Type: Bug Components: ambari-server Reporter: Chen He
Without specify any configuration, the hadoop-env.sh which is generated by Ambari like: export HADOOP_NAMENODE_INIT_HEAPSIZE="-Xms1024" export HADOOP_NAMENODE_OPTS="-server -XX:ParallelGCThreads=8 -XX:+UseConcMarkSweepGC -XX:ErrorFile=/var/log/hadoop/$USER/hs_err_pid%p.log -XX:NewSize=200 -XX:MaxNewSize=200 -Xloggc:/var/log/hadoop/$USER/gc.log-`date +'%Y%m%d%H%M'` -verbose:gc -XX:+PrintGCDetails -XX:+PrintGCTimeStamps -XX:+PrintGCDateStamps -Xms1024 -Xmx1024 -Dhadoop.security.logger=INFO,DRFAS -Dhdfs.audit.logger=INFO,DRFAAUDIT -Dnamenode.metrics.logger=INFO,NNMETRICSRFA ${HADOOP_NAMENODE_OPTS} -Dorg.mortbay.jetty.Request.maxFormContentSize=-1" export HADOOP_DATANODE_OPTS="-server -XX:ParallelGCThreads=4 -XX:+UseConcMarkSweepGC -XX:ErrorFile=/var/log/hadoop/$USER/hs_err_pid%p.log -XX:NewSize=200m -XX:MaxNewSize=200m -Xloggc:/var/log/hadoop/$USER/gc.log-`date +'%Y%m%d%H%M'` -verbose:gc -XX:+PrintGCDetails -XX:+PrintGCTimeStamps -XX:+PrintGCDateStamps -Xms1024 -Xmx1024 -Dhadoop.security.logger=INFO,DRFAS -Dhdfs.audit.logger=INFO,DRFAAUDIT ${HADOOP_DATANODE_OPTS}" To set the heap size 1024Bytes for namenode and datanodes are too small! If it is 1GB it should be "-Xmx1024m" instead of "-Xmx1024" -- This message was sent by Atlassian JIRA (v6.3.4#6332)