You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Ravi Prakash (Commented) (JIRA)" <ji...@apache.org> on 2012/03/30 17:48:31 UTC
[jira] [Commented] (HADOOP-6963) Fix FileUtil.getDU. It should not
include the size of the directory or follow symbolic links
[ https://issues.apache.org/jira/browse/HADOOP-6963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13242464#comment-13242464 ]
Ravi Prakash commented on HADOOP-6963:
--------------------------------------
@Owen : I took the liberty of editing this JIRA to include another fix in the same method.
> Fix FileUtil.getDU. It should not include the size of the directory or follow symbolic links
> --------------------------------------------------------------------------------------------
>
> Key: HADOOP-6963
> URL: https://issues.apache.org/jira/browse/HADOOP-6963
> Project: Hadoop Common
> Issue Type: Bug
> Components: fs
> Affects Versions: 0.20.205.0
> Reporter: Owen O'Malley
> Assignee: Owen O'Malley
> Priority: Critical
>
> The getDU method should not include the size of the directory. The Java interface says that the value is undefined and in Linux/Sun it gets the 4096 for the inode. Clearly this isn't useful.
> It also recursively calls itself. In case the directory has a symbolic link forming a cycle, getDU keeps spinning in the cycle. In our case, we saw this in the org.apache.hadoop.mapred.JobLocalizer.downloadPrivateCacheObjects call. This prevented other tasks on the same node from committing, causing the TT to become effectively useless (because the JT thinks it already has enough tasks running)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira