[
https://issues.apache.org/jira/browse/YARN-7848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16802178#comment-16802178
]
Eric Yang commented on YARN-7848:
---------------------------------
[~ebadger] Docker rm will use stop signal then remove the container workspace
and metadata. Docker rm -f will use SIGKILL then remove the container
workspace and metadata. In YARN ContainerCleanup, it will send stop signal if
pid exists. If not, it will run docker kill, then follow by docker rm.
Therefore, the steps leading to docker rm is identical to docker stop, docker
rm -f. There will be no process running after docker kill is ran. The
remaining task is to remove metadata from docker database. Therefore, making
distinction between first docker rm and docker rm -f become unnecessary because
YARN already performed stop, and docker kill operations.
> 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: Eric Yang
> Priority: Major
> Labels: Docker
> Attachments: YARN-7848.001.patch
>
>
> 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]
