hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] Commented: (MAPREDUCE-1914) TrackerDistributedCacheManager never cleans its input directories
Date Mon, 28 Feb 2011 01:36:37 GMT

    [ https://issues.apache.org/jira/browse/MAPREDUCE-1914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13000079#comment-13000079

Hadoop QA commented on MAPREDUCE-1914:

-1 overall.  Here are the results of testing the latest attachment 
  against trunk revision 1074251.

    +1 @author.  The patch does not contain any @author tags.

    +1 tests included.  The patch appears to include 3 new or modified tests.

    +1 javadoc.  The javadoc tool did not generate any warning messages.

    -1 javac.  The patch appears to cause tar ant target to fail.

    -1 findbugs.  The patch appears to cause Findbugs (version 1.3.9) to fail.

    +1 release audit.  The applied patch does not increase the total number of release audit

    -1 core tests.  The patch failed these core unit tests:

    -1 contrib tests.  The patch failed contrib unit tests.

    -1 system test framework.  The patch failed system test framework compile.

Test results: https://hudson.apache.org/hudson/job/PreCommit-MAPREDUCE-Build/76//testReport/
Console output: https://hudson.apache.org/hudson/job/PreCommit-MAPREDUCE-Build/76//console

This message is automatically generated.

> TrackerDistributedCacheManager never cleans its input directories
> -----------------------------------------------------------------
>                 Key: MAPREDUCE-1914
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-1914
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>            Reporter: Dick King
>            Assignee: Dick King
>         Attachments: MAPREDUCE-1914--2010-07-30--1336.patch
> When we localize a file into a node's cache, it's installed in a directory whose subroot
is a random {{long}} .  These {{long}} s all sit in a single flat directory [per disk, per
cluster node].  When the cached file is no longer needed, its reference count becomes zero
in a tracking data structure.  The file then becomes eligible for deletion when the total
amount of space occupied by cached files exceeds 10G [by default] or the total number of such
files exceeds 10K.
> However, when we delete a cached file, we don't delete the directory that contains it;
this importantly includes the elements of the flat directory, which then accumulate until
they reach a system limit, 32K in some cases, and then the node stops working.
> We need to delete the flat directory when we delete the localized cache file it contains.

This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message