[MESOS-4087] Introduce a module for logging executor/task output

• Type: Task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.27.0
• Component/s: containerization, modules
• Labels: logging mesosphere
• Target Version/s: 0.27.0
• Epic Link: logger module
• Sprint: Mesosphere Sprint 24, Mesosphere Sprint 25
• Story Points: 5
• Assignee: Joseph Wu
• Reporter: Joseph Wu
• Shepherd: Benjamin Hindman
• Created: 07/Dec/15 20:53
• Updated: 29/Apr/19 09:26
• Resolved: 26/Nov/18 12:21

Description

Existing executor/task logs are logged to files in their sandbox directory, with some nuances based on which containerizer is used (see background section in linked document).

A logger for executor/task logs has the following requirements:

• The logger is given a command to run and must handle the stdout/stderr of the command.
• The handling of stdout/stderr must be resilient across agent failover. Logging should not stop if the agent fails.
• Logs should be readable, presumably via the web UI, or via some other module-specific UI.

Issue Links

• blocks: MESOS-4088 Modularize existing plain-file logging for executor/task logs launched with the Mesos Containerizer
• links to: Investigation on the state of logging in Mesos