mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Deshi Xiao (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MESOS-1871) Sending SIGTERM to a task command may render it orphaned
Date Mon, 28 Aug 2017 23:13:02 GMT

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

Deshi Xiao commented on MESOS-1871:
-----------------------------------

[~idownes] i have some cycle to work on this issue, could you please shepherd me. where is
best start on fix it?

> Sending SIGTERM to a task command may render it orphaned
> --------------------------------------------------------
>
>                 Key: MESOS-1871
>                 URL: https://issues.apache.org/jira/browse/MESOS-1871
>             Project: Mesos
>          Issue Type: Bug
>          Components: agent
>            Reporter: Alexander Rukletsov
>            Priority: Minor
>
> {{CommandExecutor}} launches tasks wrapping them into {{sh -c}}. That means signals are
sent to the top process—that is {{sh -c}}—and not to the task directly. Though {{SIGTERM}}
is propagated by {{sh -c}} down the process tree, if the task is unresponsive to {{SIGTERM}},
{{sh -c}} terminates reporting success to the {{CommandExecutor}}, rendering the task detached
from the parent process and still running. Because the {{CommandExecutor}} thinks the command
terminated normally, its OS process exits normally and may not trigger containerizer's escalation
which destroys cgroups.
> Here is the test related to the first part: [https://gist.github.com/rukletsov/68259dfb02421813f9e6].
> Here is the test related to the second part: [https://gist.github.com/rukletsov/3f19ecc7389fa51e65c0].



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

Mime
View raw message