[MESOS-6833] consecutive_failures 0 == 1 in HealthCheck.

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 0.28.0, 1.0.0, 1.1.0
• Component/s: agent
• Labels: check health-check mesosphere
• Epic Link: TaskCheckingImprovements
• Story Points: 3
• Assignee: Unassigned
• Reporter: Lukas Loesche
• Shepherd: Alex R
• Created: 22/Dec/16 14:44
• Updated: 06/Apr/17 10:52

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.

Issue Links

• relates to: MESOS-6417 Introduce an extra 'unknown' health check state.