[
https://issues.apache.org/jira/browse/MAPREDUCE-3057?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13127980#comment-13127980
]
Hudson commented on MAPREDUCE-3057:
-----------------------------------
Integrated in Hadoop-Mapreduce-trunk-Commit #1105 (See
[https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Commit/1105/])
MAPREDUCE-3057. Job History Server goes of OutOfMemory with 1200 Jobs and
Heap Size set to 10 GB. (Eric Payne via mahadev)
mahadev :
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1183545
Files :
* /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt
*
/hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-hs/src/main/java/org/apache/hadoop/mapreduce/v2/hs/JobHistory.java
> Job History Server goes of OutOfMemory with 1200 Jobs and Heap Size set to 10
> GB
> --------------------------------------------------------------------------------
>
> Key: MAPREDUCE-3057
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3057
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: jobhistoryserver, mrv2
> Affects Versions: 0.23.0
> Reporter: Karam Singh
> Assignee: Eric Payne
> Priority: Blocker
> Fix For: 0.23.0
>
> Attachments: MAPREDUCE-3057.v1.txt
>
>
> History server was started with -Xmx10000m
> Ran GridMix V3 with 1200 Jobs trace in STRESS mode on 350 nodes with each
> node 4 NMS.
> All jobs finished as reported by RM Web UI and HADOOP_MAPRED_HOME/bin/mapred
> job -list all
> But found that GridMix job client was stuck while trying connect to
> HistoryServer
> Then tried to do HADOOP_MAPRED_HOME/bin/mapred job -status jobid
> JobClient also got stuck while looking for token to connect to History server
> Then looked at History Server logs and found History is trowing
> "java.lang.OutOfMemoryError: GC overhead limit exceeded" error.
> With 10GB of Heap space and 1200 Jobs, History Server should not go out of
> memory .
> No matter what are the type of jobs.
--
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
