[
https://issues.apache.org/jira/browse/YARN-6401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15944787#comment-15944787
]
kyungwan nam commented on YARN-6401:
------------------------------------
thanks for your comment.
signal is sent to the whole process group.
so, SIGTERM will go both a front-end shell and the “real” process directly.
alternatively, we might also consider detaching the “real” process from the
front-end shell.
but, it also has problems...
the “real” process could be decoupled from container life cycle, and it would
be excepted from resource monitoring.
> terminating signal should be able to specify per application to support
> graceful-stop
> -------------------------------------------------------------------------------------
>
> Key: YARN-6401
> URL: https://issues.apache.org/jira/browse/YARN-6401
> Project: Hadoop YARN
> Issue Type: Improvement
> Reporter: kyungwan nam
>
> when stop container, first send SIGTERM to the process.
> after a while, send SIGKILL if the process is still alive.
> above process is always the same for any application.
> but, to graceful-stop, sometimes it need to send another signal instead of
> SIGTERM.
> for instance, if apache httpd on slider is running, SIGWINCH should be came
> to stop gracefully.
> the way to stop gracefully is depend on application.
> it will be good if we can define a signal to terminate per application.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
