hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eric Badger (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-4759) Fix signal handling for docker containers
Date Tue, 29 Aug 2017 16:25:01 GMT

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

Eric Badger commented on YARN-4759:

[~shanekumpf@gmail.com], is there a way in this approach to support sending signals to a running
container (e.g. SIGQUIT for jstack/heap dump)? From the code, it looks like all signals are
handled as either signal 0 or "other" with "other" stopping the container. In the case of
a jstack/heap dump we don't want to stop the container, just send the signal. If there's no
way currently, I can file a JIRA and work to support this functionality

> Fix signal handling 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
>             Fix For: 2.9.0, 3.0.0-alpha1
>         Attachments: YARN-4759.001.patch, YARN-4759.002.patch, YARN-4759.003.patch
> 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

To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org

View raw message