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 "Shane Kumpf (JIRA)" <ji...@apache.org> on 2016/04/14 23:02:26 UTC

[jira] [Commented] (YARN-4759) Revisit signalContainer() for docker containers

    [ https://issues.apache.org/jira/browse/YARN-4759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15241919#comment-15241919 ] 

Shane Kumpf commented on YARN-4759:
-----------------------------------

As I understand it, you are correct, all of the processes will be cleaned up due to PID namespaces. The challenge I was referring to is around gracefully stopping the process in the container, but after considering the options, I'm now of the opinion that this isn't something signalContainer or YARN should be concerned with. I'll post the approach I'm considering shortly.

> Revisit signalContainer() for docker containers
> -----------------------------------------------
>
>                 Key: YARN-4759
>                 URL: https://issues.apache.org/jira/browse/YARN-4759
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: yarn
>            Reporter: Sidharta Seethana
>            Assignee: Shane Kumpf
>
> The current signal handling (in the DockerContainerRuntime) needs to be revisited for docker containers. For example, container reacquisition on NM restart might not work, depending on which user the process in the container runs as. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)