You are viewing a plain text version of this content. The canonical link for it is here.

Posted to mapreduce-dev@hadoop.apache.org by "Karam Singh (JIRA)" <ji...@apache.org> on 2011/09/21 14:23:17 UTC

[jira] [Created] (MAPREDUCE-3057) Job History Server goes of OutOfMemory with 1200 Jobs and Heap Size set to 10 GB

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


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.
For more information on JIRA, see: http://www.atlassian.com/software/jira