[
https://issues.apache.org/jira/browse/HADOOP-4906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12659034#action_12659034
]
Devaraj Das commented on HADOOP-4906:
-------------------------------------
bq. I guess we need to just set defaultJobConf/localJobConf to null in
TaskInProgress.cleanup for now
+1. I would say that we also nullify the TIP.diagnosticInfo since this is user
settable too. Since a TIP has no other user settable data, and all TIPs of a
particular job are removed when the latter completes, it should be okay to keep
the TIPs in memory..
> 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
>
>
> 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.
