You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Jason Lowe (JIRA)" <ji...@apache.org> on 2017/03/27 13:58:41 UTC

[jira] [Commented] (YARN-6401) terminating signal should be able to specify per application to support graceful-stop

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

Jason Lowe commented on YARN-6401:
----------------------------------

Is this something YARN needs to support directly?  This seems straightforward to solve on the application side by wrapping the application launch with a front-end shell that traps SIGTERM and translates it into the desired signal for the "real" process.

> 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: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org