[
https://issues.apache.org/jira/browse/YARN-445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13924213#comment-13924213
]
Xuan Gong commented on YARN-445:
--------------------------------
[~mingma] I have already started to work on adding KillContainer api. I am
using the similar way as you described earlier.
Right now, if RM kill the RMContainer, and it will notice NM through the
regular heartBeat, and NM will kill the real container there. This logic has
already existed. So, I think that KillContainer might be relatively easier to
implement.
For other signals, such as SIGQUIT, SIGTERM, etc, we might need to make changes
on NM side, too.
> 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.2#6252)
