[
https://issues.apache.org/jira/browse/MESOS-7879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16128162#comment-16128162
]
Anand Mazumdar commented on MESOS-7879:
---------------------------------------
{noformat}
commit 6a1e4f7c6639ec4897c3a4a40cffea41ce302a94
Author: Anand Mazumdar <an...@apache.org>
Date: Tue Aug 15 17:41:27 2017 -0700
Added `kill()` support to the test containerizer interface.
This is needed to make some tests pass that rely on the test
containerizer.
Review: https://reviews.apache.org/r/61574/
commit 0eab58a4790f22dfc1cec70367364bdedb6024f8
Author: Anand Mazumdar <an...@apache.org>
Date: Tue Aug 15 17:38:55 2017 -0700
Added support for kill policies to the default executor.
Review: https://reviews.apache.org/r/61668/
commit d1abe1e9ae4fdd53a97e643df9b55fee969743db
Author: Anand Mazumdar <an...@apache.org>
Date: Tue Aug 15 17:38:14 2017 -0700
Made the default executor support signal escalation.
This modifies the default executor to perform signal escalation
via the 'KILL_NESTED_CONTAINER' call i.e., send a SIGTERM followed
by a SIGKILL after a constant grace period.
Review: https://reviews.apache.org/r/61573/
commit 8fc0491be86a665bb80a0dd978d8799d6559be1f
Author: Anand Mazumdar <an...@apache.org>
Date: Tue Aug 15 17:38:08 2017 -0700
Made `killNestedContainer()` use `kill()` on the containerizer.
Instead of invoking `destroy()` directly, `killNestedContainer()`
would invoke `kill()` to terminate the nested container.
Review: https://reviews.apache.org/r/61572/
commit 8c8e2af56457346af586e94f071bfa14a92eb20a
Author: Anand Mazumdar <an...@apache.org>
Date: Tue Aug 15 17:38:04 2017 -0700
Added `kill()` call to the composing containerizer.
Review: https://reviews.apache.org/r/61571/
commit 8b3fd242f4af1e2e6d7af74e865b8f42c29af3be
Author: Anand Mazumdar <an...@apache.org>
Date: Tue Aug 15 17:37:54 2017 -0700
Added the `kill()` function to the containerizer interface.
This would be used by now on for killing a container by sending
a signal to it similar to the linux equivalent `kill()` system call.
Review: https://reviews.apache.org/r/61570/
commit 093ccde55e68b705fe5ef6e851be1dc2b7e436da
Author: Anand Mazumdar <an...@apache.org>
Date: Tue Aug 15 17:37:49 2017 -0700
Added the field `signal` to the `KillNestedContainer` call.
This would be used later for sending signals (SIGTERM, SIGKILL etc.)
to the running container. Previously, SIGKILL was used by default.
Review: https://reviews.apache.org/r/61569/
{noformat}
> The kill nested container call should provide ability to specify a signal.
> --------------------------------------------------------------------------
>
> Key: MESOS-7879
> URL: https://issues.apache.org/jira/browse/MESOS-7879
> Project: Mesos
> Issue Type: Task
> Reporter: Anand Mazumdar
> Assignee: Anand Mazumdar
>
> Currently, the {{KILL_NESTED_CONTAINER}} only sends the SIGKILL signal to a
> running container. We should make it configurable and then make the default
> executor specify it i.e., initially send SIGTERM followed by a SIGTERM signal.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
