You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@mesos.apache.org by "Benjamin Mahler (JIRA)" <ji...@apache.org> on 2014/05/17 00:06:18 UTC

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

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

Benjamin Mahler updated MESOS-923:
----------------------------------

    Fix Version/s:     (was: 0.19.0)

> 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)