You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Gastón Kleiman (JIRA)" <ji...@apache.org> on 2016/08/03 10:30:20 UTC
[jira] [Commented] (MESOS-5803) Command health checks do not
survive after framework restart
[ https://issues.apache.org/jira/browse/MESOS-5803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15405694#comment-15405694 ]
Gastón Kleiman commented on MESOS-5803:
---------------------------------------
It looks like this is a bug in Marathon, not in Mesos.
The following PR should fix the Marathon bug: https://github.com/mesosphere/marathon/pull/4094
So I think we could close this JIRA.
cc/ [~alexr] [~bbannier]
> Command health checks do not survive after framework restart
> ------------------------------------------------------------
>
> Key: MESOS-5803
> URL: https://issues.apache.org/jira/browse/MESOS-5803
> Project: Mesos
> Issue Type: Bug
> Reporter: haosdent
> Labels: health-check
>
> Reported in https://github.com/mesosphere/marathon/issues/916
> and https://github.com/apache/mesos/pull/118
> So far health check only sends success healthy status if the previous status is failed or not exists. So frameworks could not know the health status of tasks after master restart.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)