[ https://issues.apache.org/jira/browse/MAPREDUCE-3954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13223205#comment-13223205 ]
Hudson commented on MAPREDUCE-3954: ----------------------------------- Integrated in Hadoop-Hdfs-0.23-Build #189 (See [https://builds.apache.org/job/Hadoop-Hdfs-0.23-Build/189/]) MAPREDUCE-3954. Added new envs to separate heap size for different daemons started via bin scripts. Contributed by Robert Joseph Evans. svn merge --ignore-ancestry -c 1297174 ../../trunk/ (Revision 1297176) Result = SUCCESS vinodkv : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1297176 Files : * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/CHANGES.txt * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/bin/mapred * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-yarn/bin/yarn * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-site/src/site/apt/ClusterSetup.apt.vm > Clean up passing HEAPSIZE to yarn and mapred commands. > ------------------------------------------------------ > > Key: MAPREDUCE-3954 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-3954 > Project: Hadoop Map/Reduce > Issue Type: Bug > Components: mrv2 > Affects Versions: 0.23.2 > Reporter: Robert Joseph Evans > Assignee: Robert Joseph Evans > Priority: Blocker > Fix For: 0.23.2 > > Attachments: MAPREDUCE-3954-20120305.txt, MR-3954.txt, MR-3954.txt, > MR-3954.txt > > > Currently the heap size for all of these is set in yarn-env.sh. > JAVA_HEAP_MAX is set to -Xmx1000m unless YARN_HEAPSIZE is set. If it is set > it will override JAVA_HEAP_MAX. However, we do not always want to have the > RM, NM, and HistoryServer with the exact same heap size. It would be logical > to have inside of yarn and mapred to set JAVA_HEAP_MAX if > YARN_RESOURCEMANAGER_HEAPSIZE, YARN_NODEMANAGER_HEAPSIZE or > HADOOP_JOB_HISTORYSERVER_HEAPSIZE are set respectively. This is a bug > because it is easy to configure the history server to store more entires then > the heap can hold. It is also a performance issue if we do not allow the > history server to cache many entries on a large cluster. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira