Mailing-List: contact issues-help@mesos.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@mesos.apache.org
Date: Mon, 20 Oct 2014 18:03:38 +0000 (UTC)
From: "Dominic Hamon (JIRA)" <jira@apache.org>
To: issues@mesos.apache.org
Message-ID: <JIRA.12744091.1411670204000.297839.1413828218003@Atlassian.JIRA>
In-Reply-To: <JIRA.12744091.1411670204000@Atlassian.JIRA>
References: <JIRA.12744091.1411670204000@Atlassian.JIRA>
 <JIRA.12744091.1411670204986@arcas>
Subject: [jira] [Updated] (MESOS-1830) Expose master stats differentiating
 between master-generated and slave-generated LOST tasks
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ 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 Q4 Sprint 2  (was: Twitter Q4 Sprint 1, Mesosphere Q4 Sprint 1)

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