[
https://issues.apache.org/jira/browse/HADOOP-4906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12663880#action_12663880
]
Sharad Agarwal commented on HADOOP-4906:
----------------------------------------
all tests passed. ant test-patch :
-1 overall.
[exec]
[exec] +1 @author. The patch does not contain any @author tags.
[exec]
[exec] -1 tests included. The patch doesn't appear to include any new
or modified tests.
[exec] Please justify why no tests are needed for
this patch.
[exec]
[exec] +1 javadoc. The javadoc tool did not generate any warning
messages.
[exec]
[exec] +1 javac. The applied patch does not increase the total number
of javac compiler warnings.
[exec]
[exec] +1 findbugs. The patch does not introduce any new Findbugs
warnings.
[exec]
[exec] +1 Eclipse classpath. The patch retains Eclipse classpath
integrity.
It is not easy to write a test case for this.
> TaskTracker running out of memory after running several tasks
> -------------------------------------------------------------
>
> Key: HADOOP-4906
> URL: https://issues.apache.org/jira/browse/HADOOP-4906
> Project: Hadoop Core
> Issue Type: Bug
> Components: mapred
> Affects Versions: 0.19.0
> Reporter: Arun C Murthy
> Assignee: Sharad Agarwal
> Priority: Blocker
> Fix For: 0.20.0
>
> Attachments: 4906_v1.patch, 4906_v2.patch, 4906_v3.patch,
> 4906_v4.patch
>
>
> Looks like the TaskTracker isn't cleaning up correctly after completed/failed
> tasks, I suspect that the JobConfs aren't being deallocated. Eventually the
> TaskTracker runs out of memory after running several tasks.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
