[MESOS-1830] Expose master stats differentiating between master-generated and slave-generated LOST tasks

• Type: Story
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: 0.22.0
• Component/s: master
• Target Version/s: 0.22.0
• Sprint: Twitter Q4 Sprint 1, Twitter Mesos Q4 Sprint 2, Twitter Mesos Q4 Sprint 3, Twitter Mesos Q4 Sprint 4, Twitter Mesos Q4 Sprint 5, Twitter Mesos Q1 Sprint 1, Twitter Mesos Q1 Sprint 2
• Story Points: 5
• Assignee: Dominic Hamon
• Reporter: Bill Farner
• Created: 25/Sep/14 18:36
• Updated: 10/Feb/15 23:23
• Resolved: 10/Feb/15 23:23

Description

The master exports a monotonically-increasing counter of tasks transitioned to TASK_LOST. This loses fidelity of the source of the lost task. A first step in exposing the source of lost tasks might be to just differentiate between TASK_LOST transitions initiated by the master vs the slave (and maybe bad input from the scheduler).

Issue Links

• is blocked by: MESOS-1972 Move TASK_LOST generations due to invalid tasks from scheduler driver to master
• is related to: MESOS-343 Expose TASK_FAILED reason to Frameworks.
• is related to: MESOS-1143 Add a TASK_ERROR task status.
• relates to: MESOS-1930 Expose TASK_KILLED reason.
• relates to: MESOS-2035 Add reason to containerizer proto Termination