[jira] [Commented] (YARN-445) Ability to signal containers

["Sandy Ryza (JIRA)" <ji...@apache.org>]

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

Sandy Ryza commented on YARN-445:
---------------------------------

In 0.21, when a task was going to be killed due to timeout, a SIGQUIT would be sent to it to dump its stacks to standard out (MAPREDUCE-1119).  This was a useful feature that I'm currently working on backporting to branch-1 in MAPREDUCE-5592.  It would be good to make sure that whatever we do here can accommodate something similar.

> Ability to signal containers
> ----------------------------
>
>                 Key: YARN-445
>                 URL: https://issues.apache.org/jira/browse/YARN-445
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: nodemanager
>            Reporter: Jason Lowe
>            Assignee: Andrey Klochkov
>         Attachments: YARN-445--n2.patch, YARN-445--n3.patch, YARN-445--n4.patch, YARN-445.patch
>
>
> It would be nice if an ApplicationMaster could send signals to contaniers such as SIGQUIT, SIGUSR1, etc.
> For example, in order to replicate the jstack-on-task-timeout feature implemented by MAPREDUCE-1119 in Hadoop 0.21 the NodeManager needs an interface for sending SIGQUIT to a container.  For that specific feature we could implement it as an additional field in the StopContainerRequest.  However that would not address other potential features like the ability for an AM to trigger jstacks on arbitrary tasks *without* killing them.  The latter feature would be a very useful debugging tool for users who do not have shell access to the nodes.



--
This message was sent by Atlassian JIRA
(v6.1#6144)