[
https://issues.apache.org/jira/browse/YARN-445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13924382#comment-13924382
]
Xuan Gong commented on YARN-445:
--------------------------------
[~mingma] The plan sounds good to me.
But I think that they are pretty big patches. Could we split them further ?
I would like to create a ticket for SIGKILL only since this is the easiest one.
We can still use SignalContainerRequest and SignalContainerResponse. Also, we
can create a enum type called SignalContainerCMD which can contains SIGKILL,
SIGTERM, etc.
After that ticket, I expect that we will have a general framework on how we
will handle the different signal on RM side. Then we can add other signal
commands, and do the related changes on NM side.
What do you think ?
> 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: MRJob.png, MRTasks.png, YARN-445--n2.patch,
> YARN-445--n3.patch, YARN-445--n4.patch, YARN-445.patch, YARNContainers.png
>
>
> 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)
