You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Eric Yang (JIRA)" <ji...@apache.org> on 2019/03/20 23:49:00 UTC
[jira] [Commented] (YARN-7848) Force removal of docker containers
that do not get removed on first try
[ https://issues.apache.org/jira/browse/YARN-7848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16797677#comment-16797677 ]
Eric Yang commented on YARN-7848:
---------------------------------
There are many scenarios that containers may not create properly or shutdown properly due to problems with the images themselves. Application-lifecycles doesn't cover all abnormal cases. It looks like we need a background thread to run:
{code}
docker container prune --filter="until=15m" -a
{code}
Every 10 minutes. This will ensure the dangling containers have max life time no older than 15 minutes.
> 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: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org