[ 
https://issues.apache.org/jira/browse/MESOS-6417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16663955#comment-16663955
 ] 

Greg Mann commented on MESOS-6417:
----------------------------------

[~urbanserj] unfortunately I think that solution wouldn't work, since it's a 
breaking API change. There could be frameworks which react upon the first 
'false' health check detected, and if we alter the time at which we populate 
that field it could break such deployments.

> Introduce an extra 'unknown' health check state.
> ------------------------------------------------
>
>                 Key: MESOS-6417
>                 URL: https://issues.apache.org/jira/browse/MESOS-6417
>             Project: Mesos
>          Issue Type: Improvement
>            Reporter: Alexander Rukletsov
>            Assignee: Greg Mann
>            Priority: Major
>              Labels: health-check, mesosphere
>
> There are three logical states regarding health checks:
> 1) no health checks;
> 2) a health check is defined, but no result is available yet;
> 3) a health check is defined, it is either healthy or not.
> Currently, we do not distinguish between 1) and 2), which can be problematic 
> for framework authors.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to