[jira] [Resolved] (HADOOP-2837) JobTracker got stuck

["Harsh J (Resolved) (JIRA)" <ji...@apache.org>]

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

Harsh J resolved HADOOP-2837.
-----------------------------

    Resolution: Fixed

This has gone stale. FWIW, I've never seen an OOM hang on the clusters in the last one and half year. Crashes most of the time there's a leak or an overload in JIP retention (tweakable).
                
> JobTracker got stuck 
> ---------------------
>
>                 Key: HADOOP-2837
>                 URL: https://issues.apache.org/jira/browse/HADOOP-2837
>             Project: Hadoop Common
>          Issue Type: Bug
>    Affects Versions: 0.15.3
>            Reporter: Runping Qi
>
> When a job tracker ran a job with a lot of map tasks,
> the commit thread complained out of memory:
> 2008-02-14 02:52:13,809 ERROR org.apache.hadoop.mapred.JobTracker: Task Commit Thread got an exception: java.lang.OutOfMemoryError: Java heap space
> 2008-02-14 02:53:18,543 ERROR org.apache.hadoop.mapred.JobTracker: Task Commit Thread got an exception: java.lang.OutOfMemoryError: Java heap space
> 2008-02-14 02:53:26,965 ERROR org.apache.hadoop.mapred.JobTracker: Task Commit Thread got an exception: java.lang.OutOfMemoryError: Java heap space
> 2008-02-14 02:54:27,009 ERROR org.apache.hadoop.mapred.JobTracker: Task Commit Thread got an exception: java.lang.OutOfMemoryError: Java heap space
> then later, the job tracker stopped making any progress, and stopped responding web GUI.

--
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