[
https://issues.apache.org/jira/browse/YARN-5670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16797855#comment-16797855
]
Chandni Singh commented on YARN-5670:
-------------------------------------
{quote}
it is possible that some images tracking are lost from LRU and result in
dangling images over time.
{quote}
The cache can be backed by NMStateStore so even when the NM comes back or is
restarted, it will know what images it localized.
The reason I am against using {{docker image prune}} is because there can be
multiple images on that node which an admin may have pulled explicitly or some
other process may have downloaded. Now, even if they don't use it within the
last {{24 h}} or whatever time we have configured for the NM, the NM should not
be the one deciding to remove that image. It is surprising for the admin/other
process that the image they pulled is being mysteriously deleted.
> Add support for Docker image clean up
> -------------------------------------
>
> Key: YARN-5670
> URL: https://issues.apache.org/jira/browse/YARN-5670
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: yarn
> Reporter: Zhankun Tang
> Assignee: Eric Yang
> Priority: Major
> Labels: Docker
> Attachments: Localization Support For Docker Images_002.pdf
>
>
> Regarding to Docker image localization, we also need a way to clean up the
> old/stale Docker image to save storage space. We may extend deletion service
> to utilize "docker rm" to do this.
> This is related to YARN-3854 and may depend on its implementation. Please
> refer to YARN-3854 for Docker image localization details.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
