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

["Vinod Kumar Vavilapalli (JIRA)" <ji...@apache.org>]

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

Vinod Kumar Vavilapalli commented on YARN-445:
----------------------------------------------

Folks, I just made YARN-1515 a sub-tasks of this.

This JIRA is today focusing on exposing a signalling interface on the ResourceManager. It seems like we can simply expose the same API as part of ContainerManagement and get most of the thread-dump functionality with minimal changes.

> 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-signal-container-via-rm.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)