[
https://issues.apache.org/jira/browse/HADOOP-3762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12614546#action_12614546
]
Tsz Wo (Nicholas), SZE commented on HADOOP-3762:
------------------------------------------------
{code}
//in FileSystem.java
protected void checkPath(Path path) {
URI uri = path.toUri();
if (uri.getScheme() == null) // fs is relative
return;
String thisScheme = this.getUri().getScheme();
String thatScheme = uri.getScheme();
String thisAuthority = this.getUri().getAuthority();
String thatAuthority = uri.getAuthority();
//authority and scheme are not case sensitive
if (thisScheme.equalsIgnoreCase(thatScheme)) {// schemes match
if (thisAuthority == thatAuthority || // & authorities match
(thisAuthority != null &&
thisAuthority.equalsIgnoreCase(thatAuthority)))
return;
if (thatAuthority == null && // path's authority is null
thisAuthority != null) { // fs has an authority
URI defaultUri = getDefaultUri(getConf()); // & is the default fs
if (thisScheme.equalsIgnoreCase(defaultUri.getScheme()) &&
thisAuthority.equalsIgnoreCase(defaultUri.getAuthority()))
return;
}
throw new IllegalArgumentException("Wrong FS: "+path+
", expected: "+this.getUri());
}
}
{code}
FileSystem.checkPath(Path path) seems having another problem that if the path
has a different scheme, the path passes the check.
> 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: Doug Cutting
> 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.
