[MESOS-2035] Add reason to containerizer proto Termination

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.21.0
• Fix Version/s: 0.26.0
• Component/s: agent
• Labels: twitter
• Epic Link: Oversubscription
• Sprint: Twitter Mesos Q3 Sprint 5, Twitter Mesos Q3 Sprint 6
• Story Points: 5
• Assignee: Jie Yu
• Reporter: Dominic Hamon
• Shepherd: Benjamin Mahler
• Created: 03/Nov/14 22:29
• Updated: 21/Dec/15 21:24
• Resolved: 13/Oct/15 00:14

Description

When an isolator kills a task, the reason is unknown. As part of MESOS-1830, the reason is set to a general one but ideally we would have the termination reason to pass through to the status update.

Issue Links

• is related to: MESOS-2020 mesos should send docker failure messages to scheduler
• is related to: MESOS-2200 bogus docker images result in bad error message to scheduler
• is related to: MESOS-2954 Remove killed from Termination protobuf message.
• is related to: MESOS-343 Expose TASK_FAILED reason to Frameworks.
• is related to: MESOS-1830 Expose master stats differentiating between master-generated and slave-generated LOST tasks
• is related to: MESOS-2657 Support multiple reasons in status update message.
• is related to: AURORA-1033 Use mesos' disk quota enforcement
• supercedes: MESOS-3593 Propagate Isolator::prepare() failures to the framework
• links to: Status update for non-terminal tasks when a container terminates