[jira] [Updated] (MESOS-7951) Extend the KillPolicy

["Vinod Kone (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/MESOS-7951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vinod Kone updated MESOS-7951:
------------------------------
    Sprint: Mesosphere Sprint 63, Mesosphere Sprint 64, Mesosphere Sprint 66  (was: Mesosphere Sprint 63, Mesosphere Sprint 64)

> Extend the KillPolicy
> ---------------------
>
>                 Key: MESOS-7951
>                 URL: https://issues.apache.org/jira/browse/MESOS-7951
>             Project: Mesos
>          Issue Type: Improvement
>          Components: agent, executor, HTTP API
>            Reporter: Greg Mann
>            Assignee: Greg Mann
>              Labels: mesosphere
>
> After introducing the {{KillPolicy}} in MESOS-4909, some interactions with framework developers have led to the suggestion of a couple possible improvements to this interface. Namely,
> * Allowing the framework to specify a command to be run to initiate termination, rather than a signal to be sent, would allow some developers to avoid wrapping their application in a signal handler. This is useful because a signal handler wrapper modifies the application's process tree, which may make introspection and debugging more difficult in the case of well-known services with standard debugging procedures.
> * In the case of terminations which do begin with a signal, it would be useful to allow the framework to specify the signal to be sent, rather than assuming SIGTERM. PostgreSQL, for example, permits several shutdown types, each initiated with a [different signal|https://www.postgresql.org/docs/9.3/static/server-shutdown.html].



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)