[
https://issues.apache.org/jira/browse/YARN-7848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16812730#comment-16812730
]
Eric Badger commented on YARN-7848:
-----------------------------------
bq. Changing this can have dicey outcome and not backward compatible. I am
likely to have to use cmd file serialization structure to pass the force option
from Java to container-executor for safety reasons.
Yea that makes sense. I thought we were already using the .cmd file with
remove-docker-container. Ok, given that reasoning I'm alright keeping the Java
code as it is and making the code changes all in the container-executor.
> 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
