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

Steve Loughran commented on YARN-445:
-------------------------------------

c-break is special in that it can talk to the whole process group:  
[http://msdn.microsoft.com/en-us/library/windows/desktop/ms683155(v=vs.85).aspx]

process-group signalling should be good (make it an option from the sender?) so 
that I can send a signal to a process started by its own bash script (e.g. 
bin/hbase->java). However, we do need to remember that some recent ubuntu 
versions (mistakenly) require a -- between signal and process group id

This is quite a significant patch -and it adds a feature that many will find 
useful - but it its going to need careful review by the YARN experts (of which 
I am not). Some quick points
# I wouldn't mark the interface/methods as stable yet
# some of the diffs in the tests look bigger than they should be 
-reformatting/refactoring? It just makes it harder to distinguish changes. 
Ideally all the existing tests should be left alone (that way we can be 
confident that they will catch regressions), with new tests underneath or in 
their own class

> 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
>         Attachments: YARN-445--n2.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