[
https://issues.apache.org/jira/browse/HADOOP-3670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12610676#action_12610676
]
amareshwari edited comment on HADOOP-3670 at 7/4/08 10:15 PM:
--------------------------------------------------------------------------
Here is a patch for branch 0.17, which makes the references to RawSplit as null
in MapTask and JIP, after the job completion.
I've not tested the patch yet.
Christian, can you please use this patch and see if it is still failing with
OutOfMemory error?
And also, can you try making _mapred.jobtracker.completeuserjobs.maximum_
lower?
was (Author: amareshwari):
Here is a patch making the references to RawSplit as null in MapTask and
JIP.
I've not tested the patch yet.
Christian, can you please use this patch and see if it is still failing with
OutOfMemory error?
And also, can you try making _mapred.jobtracker.completeuserjobs.maximum_
lower?
> JobTracker running out of heap space
> ------------------------------------
>
> Key: HADOOP-3670
> URL: https://issues.apache.org/jira/browse/HADOOP-3670
> Project: Hadoop Core
> Issue Type: Bug
> Components: mapred
> Affects Versions: 0.17.0
> Reporter: Christian Kunz
> Assignee: Amareshwari Sriramadasu
> Attachments: memory-dump.txt, patch-3670-0.17.txt
>
>
> The JobTracker on our 0.17.0 installation runs out of heap space rather
> quickly, with less than 100 jobs (at one time even after just 16 jobs).
> Running in 64-bit mode with larger heap space does not help -- it will use up
> all available RAM.
> 2008-06-28 05:17:06,661 INFO org.apache.hadoop.ipc.Server: IPC Server handler
> 62 on 9020, call he
> artbeat([EMAIL PROTECTED], false, true, 17384) from xxx.xxx.xxx.xxx
> :51802: error: java.io.IOException: java.lang.OutOfMemoryError: GC overhead
> limit exceeded
> java.io.IOException: java.lang.OutOfMemoryError: GC overhead limit exceeded
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
