[
https://issues.apache.org/jira/browse/MESOS-3599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14947523#comment-14947523
]
Erhan Kesken commented on MESOS-3599:
-------------------------------------
I think second way seems best option, keeping compatibility with old health
check commands, prevents confusion, simplifying workaround code without
breaking old ones.
only drawback is disturbing 0.23.1 and 0.24.1 users, but probably they are
minority, if you can distrubute 0.23.2 and 0.24.2 relesases fast for this
issue, people may not be aware of this temporary behavior change.
> COMMAND health checks with marathon running in slave context broken
> -------------------------------------------------------------------
>
> Key: MESOS-3599
> URL: https://issues.apache.org/jira/browse/MESOS-3599
> Project: Mesos
> Issue Type: Bug
> Affects Versions: 0.23.0
> Reporter: Erhan Kesken
> Assignee: haosdent
> Priority: Critical
>
> When deploying Mesos 0.23rc4 with latest Marathon 0.10.0 RC3 command health
> check stop working. Rolling back to Mesos 0.22.1 fixes the problem.
> Containerizer is Docker.
> All packages are from official Mesosphere Ubuntu 14.04 sources.
> The issue must be analyzed further.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
