[
https://issues.apache.org/jira/browse/MESOS-3136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14700438#comment-14700438
]
Marco Massenzio commented on MESOS-3136:
----------------------------------------
Just noticed this entirely randomly...
I would strongly suggest to avoid skipping a version between 0.22 / 0.24 as the
Leader Election would be terminally broken: we transitioned to JSON in ZK for
{{MasterInfo}} and while the 0.22 --> 0.23 --> 0.24 chain all works just fine,
skipping 0.23 would create no end of grief.
(I'm almost sure other stuff around HTTP API would break, but not sure there).
My 2c
> COMMAND health checks with Marathon 0.10.0 are broken
> -----------------------------------------------------
>
> Key: MESOS-3136
> URL: https://issues.apache.org/jira/browse/MESOS-3136
> Project: Mesos
> Issue Type: Bug
> Affects Versions: 0.23.0
> Reporter: Dr. Stefan Schimanski
> Assignee: haosdent
> Priority: Critical
> Labels: mesosphere
>
> 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)
