[
https://issues.apache.org/jira/browse/YARN-445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey Klochkov updated YARN-445:
---------------------------------
Attachment: YARN-445--n4.patch
Attaching a patch which implements Ctrl+C and uses it instead of Signal.TERM on
Windows. I tested it by manually invoking winutils.exe only. Never could
succeed with starting Hadoop itself on Windows, although tried hard.
I think it doesn't makes much sense to separate this into two patches for this
Jira and MAPREDUCE-5387.
One problem I am not able to solve is the case when a batch script is used to
start a container. Using console handlers in that case leads to batch script
waiting for "Terminate batch job? Y/N". Even if I know that a particular
process in the Job Object is a batch script I can't avoid sending the console
event to it. This may be a problem in scenarios when QUIT/TERM signals are not
followed later by KILL, and the process would not exit normally as it should.
So the question is whether KILL is used in all cases when containers are
stopped? Please advise.
> 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--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)
