mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dr. Stefan Schimanski (JIRA)" <>
Subject [jira] [Commented] (MESOS-3136) COMMAND health checks with Marathon 0.10.0rc3 are broken
Date Sat, 25 Jul 2015 13:37:04 GMT


Dr. Stefan Schimanski commented on MESOS-3136:

[~tnachen] I think you hit the nail on the head. The issue I have encountered is exactly that:
the new docker executor does not support the task health checks yet, the old one in 0.22 did.

Now the actual problem is that Marathon supports those COMMAND health checks for a long time
and people use it a lot. Hence, this looks like a regression in 0.23+ for the Marathon users.

Would it be feasible to fix that by taking (or refactoring) the launcher/executor.cpp code
for the docker executor? Or in fact, it would be even more awesome (although also kind of
incompatible with the old behavior) if the new docker executor could execute the health checks
inside the corresponding container via "docker exec". Kubernetes is following this route as

> COMMAND health checks with Marathon 0.10.0rc3 are broken
> --------------------------------------------------------
>                 Key: MESOS-3136
>                 URL:
>             Project: Mesos
>          Issue Type: Bug
>    Affects Versions: 0.23.0
>            Reporter: Dr. Stefan Schimanski
> 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

View raw message