Varun Saxena commented on YARN-2902:

bq. We still need to do this for APPLICATION resources. It is true that those 
resources will be cleaned up when the application finishes, but that could be 
hours or days later. 
Take your point. Will handle it.

bq. I think the cleanest approach is to make sure we send an event to the 
LocalizedResource when a container localizer

Will investigate further on PUBLIC resources by tomorrow and update if I find 
any flow where public resources can be orphaned.

> Killing a container that is localizing can orphan resources in the 
> ------------------------------------------------------------------------------------
>                 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
>            Assignee: Varun Saxena
>             Fix For: 2.7.0
>         Attachments: YARN-2902.002.patch, YARN-2902.patch
> 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

Reply via email to