You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Nishant Suneja (JIRA)" <ji...@apache.org> on 2014/12/28 06:29:13 UTC

[jira] [Assigned] (MESOS-1819) Ignore signals during executor critical startup

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

Nishant Suneja reassigned MESOS-1819:
-------------------------------------

    Assignee: Nishant Suneja

> Ignore signals during executor critical startup
> -----------------------------------------------
>
>                 Key: MESOS-1819
>                 URL: https://issues.apache.org/jira/browse/MESOS-1819
>             Project: Mesos
>          Issue Type: Bug
>          Components: containerization, isolation, slave
>            Reporter: Tobias Weingartner
>            Assignee: Nishant Suneja
>            Priority: Minor
>
> If the slave receives a SIGTERM between the time that it checkpoints a PID of a new task/container, and the time that the container is fully functional, the task will end up getting lost upon recovery.
> Possibly handle this via either a graceful shutdown hook (via signal handler, or possibly web endpoint), or possibly defer signals during the critical section.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)