[ https://issues.apache.org/jira/browse/YARN-8744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Eric Badger updated YARN-8744: ------------------------------ Issue Type: Sub-task (was: Improvement) Parent: YARN-8472 > In some cases docker kill is used to stop non-privileged containers instead > of sending the signal directly > ---------------------------------------------------------------------------------------------------------- > > Key: YARN-8744 > URL: https://issues.apache.org/jira/browse/YARN-8744 > Project: Hadoop YARN > Issue Type: Sub-task > Reporter: Chandni Singh > Assignee: Chandni Singh > Priority: Major > Labels: docker > > With YARN-8706, stopping docker containers was achieved by > 1. parsing the user specified {{STOPSIGNAL}} via docker inspect > 2. executing {{docker kill --signal=<STOPSIGNAL>}} > Quoting [~ebadger] > {quote} > Additionally, for non-privileged containers, we don't need to call docker > kill. Instead, we can follow the code in handleContainerKill() and send the > signal directly. I think this code could probably be combined, since at this > point handleContainerKill() and handleContainerStop() will be doing the same > thing. The only difference is that the STOPSIGNAL will be used for the stop. > {quote} > To achieve the above, we need native code that accepts the name of the signal > rather than the value (number) of the signal. -- 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