mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vinod Kone (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MESOS-1830) Expose master stats differentiating between master-generated and slave-generated LOST tasks
Date Thu, 09 Oct 2014 01:16:34 GMT

    [ https://issues.apache.org/jira/browse/MESOS-1830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14164536#comment-14164536
] 

Vinod Kone commented on MESOS-1830:
-----------------------------------

I added a proposal for how it could look in the attached review. Please take a look. 

Feedback welcome on the review or here.

> 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
>            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)

Mime
View raw message