[jira] [Commented] (MESOS-7411) Frameworks may specify alternate "stop" signal vs. SIGTERM

["James DeFelice (JIRA)" <ji...@apache.org>]

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

James DeFelice commented on MESOS-7411:
---------------------------------------

Related Docker feature: https://docs.docker.com/engine/reference/commandline/run/#stop-container-with-signal---stop-signal

> Frameworks may specify alternate "stop" signal vs. SIGTERM
> ----------------------------------------------------------
>
>                 Key: MESOS-7411
>                 URL: https://issues.apache.org/jira/browse/MESOS-7411
>             Project: Mesos
>          Issue Type: Improvement
>            Reporter: James DeFelice
>              Labels: mesosphere
>
> Normally Mesos sends a {{SIGTERM}} that escalates to {{SIGKILL}} when stopping a running process. Some apps handle {{SIGTERM}} differently and expose "stop" behavior via an alternate signal, for example {{SIGRTMIN+3}} (looking at you, systemd). It should be possible for a framework to specify an alternate "stop" signal via the Mesos API, which Mesos would then send to a process when attempting to stop it (before escalating to {{SIGKILL}}).



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)