[
https://issues.apache.org/jira/browse/HADOOP-3670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12611419#action_12611419
]
Hadoop QA commented on HADOOP-3670:
-----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12385383/patch-3670.txt
against trunk revision 674645.
+1 @author. The patch does not contain any @author tags.
-1 tests included. The patch doesn't appear to include any new or modified
tests.
Please justify why no tests are needed for this patch.
+1 javadoc. The javadoc tool did not generate any warning messages.
+1 javac. The applied patch does not increase the total number of javac
compiler warnings.
+1 findbugs. The patch does not introduce any new Findbugs warnings.
+1 release audit. The applied patch does not increase the total number of
release audit warnings.
-1 core tests. The patch failed core unit tests.
-1 contrib tests. The patch failed contrib unit tests.
Test results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2805/testReport/
Findbugs warnings:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2805/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2805/artifact/trunk/build/test/checkstyle-errors.html
Console output:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2805/console
This message is automatically generated.
> 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
> Fix For: 0.19.0
>
> Attachments: memory-dump.txt, patch-3670-0.17-v2.txt,
> patch-3670-0.17.txt, patch-3670.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.
