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

consecutive_failures 0 == 1 in HealthCheck.

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 0.28.0, 1.0.0, 1.1.0
    • Fix Version/s: None
    • Component/s: 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

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                lloesche Lukas Loesche
                Shepherd:
                Alex R
              • Votes:
                0 Vote for this issue
                Watchers:
                5 Start watching this issue

                Dates

                • Created:
                  Updated: