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

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

Sorry for jumping real late on this. I see Andrey has been working on patches, 
but haven't looked at them. Trying to see if we are doing it right.

bq. Add YARN API support for ContainerLaunchContext to accept a mapping of 
externally-triggered command names to code. (i.e. 
ctx.setExternalCommand("gracefulShutdown", "kill -TERM $CONTAINER_PID").
I think this is a better approach overall. We already support running arbitrary 
command-lines as part of start-container. Even without signalling, we have a 
stopContainer API which clearly indicates that the container be shut-down. 
Either via a flag or a new API, for signalling containers, why don't we just 
implement it as an additional command that is run on the NM. NM can provide 
important information, like user-name, pid, pgrpid, sid etc in a platform 
agnostic manner for that command and we should be all done?

> 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)

Reply via email to