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

consecutive_failures 0 == 1 in HealthCheck.

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

Details

    • Bug
    • Status: Open
    • Major
    • Resolution: Unresolved
    • 0.28.0, 1.0.0, 1.1.0
    • None
    • agent

    Description

      When defining a HealthCheck with consecutive_failures=0 one would expect Mesos to never kill the task and only notify about the failure.

      What seems to happen instead is Mesos handles consecutive_failures=0 as consecutive_failures=1 and kills the task after 1 failure.

      Since 0 isn't the same as 1 this seems to be a bug and results in unexpected behaviour.

      Attachments

        Issue Links

        relates to

        Improvement - An improvement or enhancement to an existing feature or task. MESOS-6417 Introduce an extra 'unknown' health check state.

        • Major - Major loss of function.
        • Accepted

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

          People

            Unassigned Unassigned
            lloesche Lukas Loesche
            Alex R Alex R
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:

              Slack

                Issue deployment