[
https://issues.apache.org/jira/browse/MAPREDUCE-2495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Douglas updated MAPREDUCE-2495:
-------------------------------------
Resolution: Fixed
Fix Version/s: 0.23.0
0.20.205.0
Hadoop Flags: [Reviewed]
Status: Resolved (was: Patch Available)
+1
I committed this. Thanks, Robert!
> 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
> Fix For: 0.20.205.0, 0.23.0
>
> Attachments: MAPREDUCE-2495-20.20X-V1.patch,
> MAPREDUCE-2495-20.20X-V2.patch, MAPREDUCE-2495-20.20X-V3.patch,
> MAPREDUCE-2495-20.20X-V4.patch, MAPREDUCE-2495-v1.patch,
> MAPREDUCE-2495-v2.patch, MAPREDUCE-2495-v3.patch, MAPREDUCE-2495-v4.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
