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

["Eric Payne (Updated) (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/MAPREDUCE-3057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Eric Payne updated MAPREDUCE-3057:
----------------------------------

    Attachment: MAPREDUCE-3057.v1.txt

I'm having trouble reproducing this on my 1-node cluster. I'm continuing to try to test this, but since it's just a change to the default config value, I think it's safe to just post the patch and make sure this is what was agreed to.
                
> 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