[
https://issues.apache.org/jira/browse/MAPREDUCE-2495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13034827#comment-13034827
]
Hadoop QA commented on MAPREDUCE-2495:
--------------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12479465/MAPREDUCE-2495-20.20X-V1.patch
against trunk revision 1103993.
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 3 new or modified tests.
-1 patch. The patch command could not apply the patch.
Console output:
https://builds.apache.org/hudson/job/PreCommit-MAPREDUCE-Build/257//console
This message is automatically generated.
> The distributed cache cleanup thread has no monitoring to check to see if it
> has died for some reason
> -----------------------------------------------------------------------------------------------------
>
> Key: MAPREDUCE-2495
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-2495
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: distributed-cache
> Affects Versions: 0.21.0
> Reporter: Robert Joseph Evans
> Assignee: Robert Joseph Evans
> Priority: Minor
> Attachments: MAPREDUCE-2495-20.20X-V1.patch, MAPREDUCE-2495-v1.patch
>
>
> The cleanup thread in the distributed cache handles IOExceptions and the like
> correctly, but just to be a bit more defensive it would be good to monitor
> the thread, and check that it is still alive regularly, so that the
> distributed cache does not fill up the entire disk on the node.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
