[
https://issues.apache.org/jira/browse/YARN-2902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14951034#comment-14951034
]
Varun Saxena commented on YARN-2902:
------------------------------------
[~jlowe],
bq. We also don't need delayed deletion support in DeletionService, since we
know the container localizer process is dead.
Localizer doesnt exit immediately as of now when container is killed, even
though we interrupt the thread. We first issue a DIE on next HB and then only
localizer exits.
>From the time container is killed and localizer exits, a resource maybe
>downloaded or may start downloading. We will delete the tmp directory and main
>directory.
But if download is started by localizer in the meantime, it will recreate the
directories (in FSDownload#call).
That is why delay has been introduced. Thoughts ?
> 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
> Assignee: Varun Saxena
> Attachments: YARN-2902.002.patch, YARN-2902.03.patch,
> YARN-2902.04.patch, YARN-2902.05.patch, YARN-2902.06.patch,
> YARN-2902.07.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
(v6.3.4#6332)
