[
https://issues.apache.org/jira/browse/YARN-4759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15208622#comment-15208622
]
Shane Kumpf commented on YARN-4759:
-----------------------------------
Also of note, we should propagate the return code that killed the container up
to the end user to allow them to ensure that an exotic signal handling worked
appropriately. This can be achieved through getting the return code from the
container and subtracting 128 to get the actual signal sent.
{code}
docker inspect -f '{{.State.ExitCode}}' <container id>
{code}
> 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)
