[
https://issues.apache.org/jira/browse/MESOS-6204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15519399#comment-15519399
]
Jie Yu commented on MESOS-6204:
-------------------------------
commit 972f118006c2a00854a628d499be4ad6dbf2c61f
Author: Kevin Klues <klue...@gmail.com>
Date: Sat Sep 24 10:58:37 2016 -0700
Added helpers for maintaining files in a container runtime directory.
Review: https://reviews.apache.org/r/52013/
> Introduce a "runtime" directory owned by the containerizer for checkpointing
> container information.
> ---------------------------------------------------------------------------------------------------
>
> Key: MESOS-6204
> URL: https://issues.apache.org/jira/browse/MESOS-6204
> Project: Mesos
> Issue Type: Task
> Reporter: Kevin Klues
> Assignee: Kevin Klues
> Fix For: 1.1.0
>
>
> Currently the containerizer optionally checkpoints the container pid into the
> agent meta directory if requested by the agent. Moveing forward, we would
> like to have a containerizer-specific runtime directory where the
> containerizer will checkpoint any container state it would like to maintain
> independent of the agent container information that it checkpoints.
> Currently, this will include the container pid as well as the container exit
> status. In conjunction with the changes to the launch helper introduced by
> MESOS-6088, the containerizer will now be able to better recover the
> container exit status if it happens to be offline at the time that a
> container finishes.
> This includes being able to reap the exit status from a checkpointed location
> in addition to reading it directly from the container as it exits.
> Originally we were planning on pushing some of this functionality down into
> the LinuxLauncher, but in the end we decided it made more sense to keep all
> checkpointing information in the containerizer itself. We will likely
> revisit this decision in the future.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
