[
https://issues.apache.org/jira/browse/HADOOP-3762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doug Cutting updated HADOOP-3762:
---------------------------------
Attachment: HADOOP-3762.patch
Here's a potential patch. (I've not tested it yet.)
The problem is that the FileSystem cache uses two different keys: one created
from the URI the user passes in and one created from the URI that the
FileSystem implementation returns to describe itself.
This patch changes that, so the user-provided URI is always used. Ideally we
could use the normalized form that the FileSystem provides, but we don't yet
have a FileSystem instance when we're performing cache lookups.
> Task tracker died due to OOM
> -----------------------------
>
> Key: HADOOP-3762
> URL: https://issues.apache.org/jira/browse/HADOOP-3762
> Project: Hadoop Core
> Issue Type: Bug
> Reporter: Runping Qi
> Assignee: Tsz Wo (Nicholas), SZE
> Priority: Blocker
> Fix For: 0.18.0
>
> Attachments: 3762_20080715.patch, 3762_20080715b.patch,
> 3762_20080715c.patch, HADOOP-3762.patch, TaskTrackerStackTrace.txt
>
>
> When running about 100 moderate jobs on a small cluster (with 19 Task
> Trackers),
> the task trackers all died due to OOM.
> I got a chance to dump the jstack strace of a task tracker before it died.
> Its image size was close 4GB!
> I saw 1200+ threads of DFSClient.LeaseChecker.
> Clearly we have a severe resource leakage problem!
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
