[
https://issues.apache.org/jira/browse/HADOOP-2837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12569363#action_12569363
]
Christian Kunz commented on HADOOP-2837:
----------------------------------------
Runping, are these mappers executing relatively fast?
As side-effect of HADOOP-2119, without any patch, our JobTracker needed at
least 2GB (1000+ node cluster, 50,000+ mappers).
> JobTracker got stuck
> ---------------------
>
> Key: HADOOP-2837
> URL: https://issues.apache.org/jira/browse/HADOOP-2837
> Project: Hadoop Core
> Issue Type: Bug
> 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.
-
You can reply to this email to add a comment to the issue online.
