You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Alexander Rukletsov (JIRA)" <ji...@apache.org> on 2016/12/22 14:54:58 UTC
[jira] [Updated] (MESOS-6833) consecutive_failures 0 == 1 in
HealthCheck.
[ https://issues.apache.org/jira/browse/MESOS-6833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alexander Rukletsov updated MESOS-6833:
---------------------------------------
Shepherd: Alexander Rukletsov
Affects Version/s: 0.28.0
1.0.0
Story Points: 3
Labels: health-check mesosphere (was: )
Summary: consecutive_failures 0 == 1 in HealthCheck. (was: consecutive_failures 0 == 1 in HealthCheck)
> consecutive_failures 0 == 1 in HealthCheck.
> -------------------------------------------
>
> Key: MESOS-6833
> URL: https://issues.apache.org/jira/browse/MESOS-6833
> Project: Mesos
> Issue Type: Bug
> Components: agent
> Affects Versions: 0.28.0, 1.0.0, 1.1.0
> Reporter: Lukas Loesche
> Labels: health-check, mesosphere
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)