[
https://issues.apache.org/jira/browse/YARN-7848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16798427#comment-16798427
]
Eric Yang commented on YARN-7848:
---------------------------------
[~ebadger] {quote}Additionally, how would this work with debug-delay? If I want
my image to stick around for awhile (or indefinitely) so that I can debug them,
how will that co-exist with this periodic pruning?{quote}
I don't have good answers for system admin allowing image dump to stick around
forever. The clean up thread is optional and configurable. The scheduling can
be based on debug-delay to ensure image is being kept for debug delay window.
This will only delete containers stuck in Created/Exited states after passing
debug-delay window.
> Force removal of docker containers that do not get removed on first try
> -----------------------------------------------------------------------
>
> Key: YARN-7848
> URL: https://issues.apache.org/jira/browse/YARN-7848
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Eric Badger
> Assignee: Zhaohui Xin
> Priority: Major
> Labels: Docker
>
> After the addition of YARN-5366, containers will get removed after a certain
> debug delay. However, this is a one-time effort. If the removal fails for
> whatever reason, the container will persist. We need to add a mechanism for a
> forced removal of those containers.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
