[
https://issues.apache.org/jira/browse/YARN-2902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14224766#comment-14224766
]
Jason Lowe commented on YARN-2902:
----------------------------------
This resource leak can be seen in the NM log when the cache cleaner runs its
cycle and tries to delete it. The NM log message will look something like this:
{noformat}
2014-11-20 23:34:49,331 [AsyncDispatcher event handler] ERROR
localizer.LocalResourcesTrackerImpl: Attempt to remove resource: { {
hdfs://x:x/x/x/x, 1416461289970, FILE, null
},pending,[],11086940691251746,DOWNLOADING} with non-zero refcount
{noformat}
And that log message will continue appear during subsequent cache cleanup
cycles.
> Killing a container that is localizing can orphan resources in the
> DOWNLOADING state
> ------------------------------------------------------------------------------------
>
> Key: YARN-2902
> URL: https://issues.apache.org/jira/browse/YARN-2902
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: nodemanager
> Affects Versions: 2.5.0
> Reporter: Jason Lowe
>
> If a container is in the process of localizing when it is stopped/killed then
> resources are left in the DOWNLOADING state. If no other container comes
> along and requests these resources they linger around with no reference
> counts but aren't cleaned up during normal cache cleanup scans since it will
> never delete resources in the DOWNLOADING state even if their reference count
> is zero.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
