Uploaded image for project: 'Mesos'
  1. Mesos
  2. MESOS-1830

Expose master stats differentiating between master-generated and slave-generated LOST tasks

Agile BoardAttach filesAttach ScreenshotVotersWatch issueWatchersLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Story
    • Status: Resolved
    • Minor
    • Resolution: Fixed
    • None
    • 0.22.0
    • master
    • None
    • 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
    • 5

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

      Attachments

        Issue Links

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            dhamon Dominic Hamon
            wfarner Bill Farner
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Agile

                Completed Sprints:
                Twitter Q4 Sprint 1 ended 20/Oct/14
                Twitter Mesos Q4 Sprint 2 ended 03/Nov/14
                Twitter Mesos Q4 Sprint 3 ended 17/Nov/14
                Twitter Mesos Q4 Sprint 4 ended 01/Dec/14
                Twitter Mesos Q4 Sprint 5 ended 15/Dec/14
                Twitter Mesos Q1 Sprint 1 ended 02/Feb/15
                Twitter Mesos Q1 Sprint 2 ended 17/Feb/15
                View on Board

                Slack

                  Issue deployment