You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@mesos.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2016/07/07 18:34:11 UTC

[jira] [Commented] (MESOS-5803) Command health checks do not survive after master restart

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

ASF GitHub Bot commented on MESOS-5803:
---------------------------------------

Github user haosdent commented on the issue:

    https://github.com/apache/mesos/pull/118
  
    Thanks @bbannier I file the ticket at https://issues.apache.org/jira/browse/MESOS-5803 , let's continue the discussion there.


> Command health checks do not survive after master 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)