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 "Chandni Singh (JIRA)" <ji...@apache.org> on 2018/09/04 21:53:00 UTC

[jira] [Updated] (YARN-8744) To stop non-privileged containers docker kill is used instead of sending the signal directly

     [ https://issues.apache.org/jira/browse/YARN-8744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chandni Singh updated YARN-8744:
--------------------------------
    Labels: docker  (was: )

> To stop non-privileged containers docker kill is used instead of sending the signal directly
> --------------------------------------------------------------------------------------------
>
>                 Key: YARN-8744
>                 URL: https://issues.apache.org/jira/browse/YARN-8744
>             Project: Hadoop YARN
>          Issue Type: Improvement
>            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-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org