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

Introduce "global" decision policy for unhealthy tasks.

Attach filesAttach ScreenshotAdd voteVotersWatch issueWatchersLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Open
    • Major
    • Resolution: Unresolved
    • 1.0.0
    • None
    • None

    Description

      Currently, if the task is deemed unhealthy, i.e. it failed a health check a certain number of times, it is killed by both default executors: command and docker. This is what can be called "local" kill policy.

      While local kill policy can save some network traffic and unload the scheduler, there are cases, when a scheduler may want to decide what—and when—to do. This is what can be called "global" policy, i.e. the health check library reports whether a health check failed or succeeded, while the executor forwards this update to the scheduler without taking any action.

      Attachments

        Activity

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

          People

            Unassigned Unassigned
            alexr Alex R
            Alex R Alex R

            Dates

              Created:
              Updated:

              Agile

                Completed Sprint:
                Mesosphere Sprint 44 ended 14/Oct/16
                View on Board

                Slack

                  Issue deployment