[
https://issues.apache.org/jira/browse/MESOS-1031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13930678#comment-13930678
]
Timothy St. Clair commented on MESOS-1031:
------------------------------------------
+1 I think as long as there is a change-log that outlines the behavioral
differences then that should be sufficient. Trying to create equivalence
across disparate platforms can be quite difficult, as long as it's "good
enough". In this case I think process groups is likely "good enough"
> Command executor should support signal escalation.
> --------------------------------------------------
>
> Key: MESOS-1031
> URL: https://issues.apache.org/jira/browse/MESOS-1031
> Project: Mesos
> Issue Type: Improvement
> Components: slave
> Reporter: Niklas Quarfot Nielsen
>
> To make command executor shutdown more graceful, the sequence could allow
> signal escalation with initial SIGTERM followed by SIGKILL after an
> appropriate timeout. This became apparent when we where using the command
> executor for pluggable containerization (see
> https://issues.apache.org/jira/browse/MESOS-816).
> The escalation would need to prevent shutdown of the command executor until
> child processes have actually stopped and if processes are still alive after
> the timeout, send SIGKILL to the original process group.
> Further more, additional unit tests could be added to verify the new
> escalation i.e. add or modify a test-executor so it becomes irresponsive to
> SIGTERM and/or leaves behind orphan processes.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
