You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Joseph Wu (JIRA)" <ji...@apache.org> on 2015/12/21 01:12:46 UTC
[jira] [Updated] (MESOS-4150) Implement container logger module
metadata recovery
[ https://issues.apache.org/jira/browse/MESOS-4150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Joseph Wu updated MESOS-4150:
-----------------------------
Sprint: (was: Mesosphere Sprint 24)
> Implement container logger module metadata recovery
> ---------------------------------------------------
>
> Key: MESOS-4150
> URL: https://issues.apache.org/jira/browse/MESOS-4150
> Project: Mesos
> Issue Type: Task
> Components: modules
> Reporter: Joseph Wu
> Assignee: Joseph Wu
> Labels: logging, mesosphere
>
> The {{ContainerLoggers}} are intended to be isolated from agent failover, in the same way that executors do not crash when the agent process crashes.
> For default {{ContainerLogger}} s, like the {{SandboxContainerLogger}} and the (tentatively named) {{TruncatingSandboxContainerLogger}}, the log files are exposed during agent recovery regardless.
> For non-default {{ContainerLogger}} s, the recovery of executor metadata may be necessary to rebuild endpoints that expose the logs. This can be implemented as part of {{Containerizer::recover}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)