hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ming Ma (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-445) Ability to signal containers
Date Sat, 08 Mar 2014 03:48:56 GMT

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

Ming Ma commented on YARN-445:
------------------------------

Thanks all for the comments. I will create subtasks and feel free to add or update.

Chuan, the main proposal here is regarding which components need to be involved in container
signal support. Instead of having AM ask NM to signal the container, the proposal is to have
client ask RM which then route the request to NM; AM isn't in the picture anymore.

Xuan, Hitesh, that is a good point. While the proposal here is orthogonal to the support for
different OSs, the API using signal number has the assumption for Linux. SignalContainerCMD
sounds a good idea.

Zhijie, having "yarn container" command could be useful in the future if we decide to allow
more operations on container besides signal.



> Ability to signal containers
> ----------------------------
>
>                 Key: YARN-445
>                 URL: https://issues.apache.org/jira/browse/YARN-445
>             Project: Hadoop YARN
>          Issue Type: 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)

Mime
View raw message