[
https://issues.apache.org/jira/browse/MESOS-923?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13900761#comment-13900761
]
Till Toenshoff commented on MESOS-923:
--------------------------------------
Just to make sure I understand your improvement; would that mean the interface
for Containerizer::recover would change, barring the persisted SlaveState? I
guess so but just wanted to confirm.
> 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
> Fix For: 0.18.0
>
>
> 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.1.5#6160)
