[
https://issues.apache.org/jira/browse/YARN-4759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15218532#comment-15218532
]
Vinod Kumar Vavilapalli commented on YARN-4759:
-----------------------------------------------
bq. To complicate matters, the docker client sends signals PID 1 in the
container, so depending on if exec form is used for CMD in the Dockerfile, the
process we want to send the signal to may be a subprocess of the shell running
as PID 1.
[[email protected]], irrespective of where the signal is delivered, all the
processes and process-trees inside the container will get cleaned up, right?
For e.g, if I create a new session *inside* the container using setsid, that
will get cleaned up too?
> 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)
