[jira] [Commented] (MESOS-923) Containerizers should persist their own recovery state.

["Till Toenshoff (JIRA)" <ji...@apache.org>]

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

Till Toenshoff commented on MESOS-923:
--------------------------------------

I just closed MESOS-1328 as it appears to be a duplicate of this ticket. It just describes a symptom caused by something MESOS-923 intends to solve.

To work around the symptoms of MESOS-1328, I currently have to checkpoint such pid within the external containerizer {{launch}} to prevent a slave failure on state recovery.

> Containerizers should persist their own recovery state.
> -------------------------------------------------------
>
>                 Key: MESOS-923
>                 URL: https://issues.apache.org/jira/browse/MESOS-923
>             Project: Mesos
>          Issue Type: Improvement
>          Components: isolation
>            Reporter: Ian Downes
>
> In the current containerizer refactor (and previous process_isolator and cgroups_isolator) the forked executor pid is persisted by the MesosContainerizer but recovered with the rest of the slave state. This coupling is undesirable as containerizer implementations may or may not use the pid for recovery and may require additional, specific state for recovery.
> Instead each containerizer implementation should manage persistence of whatever state they require for recovery.



--
This message was sent by Atlassian JIRA
(v6.2#6252)