[
https://issues.apache.org/jira/browse/MESOS-1830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dominic Hamon updated MESOS-1830:
---------------------------------
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 (was: 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 Q4 Sprint 6)
> Expose master stats differentiating between master-generated and
> slave-generated LOST tasks
> -------------------------------------------------------------------------------------------
>
> Key: MESOS-1830
> URL: https://issues.apache.org/jira/browse/MESOS-1830
> Project: Mesos
> Issue Type: Story
> Components: master
> Reporter: Bill Farner
> Assignee: Dominic Hamon
> Priority: Minor
>
> 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).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
