[
https://issues.apache.org/jira/browse/MAPREDUCE-2494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13034537#comment-13034537
]
Hadoop QA commented on MAPREDUCE-2494:
--------------------------------------
+1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12479370/MAPREDUCE-2494-V1.patch
against trunk revision 1103921.
+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 applied patch does not increase the total number of javac
compiler warnings.
+1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9)
warnings.
+1 release audit. The applied patch does not increase the total number of
release audit warnings.
+1 core tests. The patch passed core unit tests.
+1 contrib tests. The patch passed contrib unit tests.
+1 system test framework. The patch passed system test framework compile.
Test results:
https://builds.apache.org/hudson/job/PreCommit-MAPREDUCE-Build/251//testReport/
Findbugs warnings:
https://builds.apache.org/hudson/job/PreCommit-MAPREDUCE-Build/251//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Console output:
https://builds.apache.org/hudson/job/PreCommit-MAPREDUCE-Build/251//console
This message is automatically generated.
> Make the distributed cache delete entires using LRU priority
> ------------------------------------------------------------
>
> Key: MAPREDUCE-2494
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-2494
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: distributed-cache
> Affects Versions: 0.21.0
> Reporter: Robert Joseph Evans
> Assignee: Robert Joseph Evans
> Attachments: MAPREDUCE-2494-V1.patch
>
>
> Currently the distributed cache will wait until a cache directory is above a
> preconfigured threshold. At which point it will delete all entries that are
> not currently being used. It seems like we would get far fewer cache misses
> if we kept some of them around, even when they are not being used. We should
> add in a configurable percentage for a goal of how much of the cache should
> remain clear when not in use, and select objects to delete based off of how
> recently they were used, and possibly also how large they are/how difficult
> is it to download them again.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
