[ https://issues.apache.org/jira/browse/YARN-7848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16812528#comment-16812528 ]
Eric Badger commented on YARN-7848: ----------------------------------- Thanks for the update, [~eyang]! On the java side, it looks like {{DockerRmCommand}} is invoked in 2 different places. Could we maintain the original constructor with no force and then add an additional constructor with a {{force}} parameter? We could then change the 2 invocations to use the new constructor with setting {{force}} to {{true}}. > 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, YARN-7848.002.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: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org