[
https://issues.apache.org/jira/browse/MESOS-3599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14946971#comment-14946971
]
Erhan Kesken commented on MESOS-3599:
-------------------------------------
I had to rollback to 0.22.2 because of this issue, I'm sharing some of our
health check commands we currently use to give you an idea about use cases:
{no-format}
# for mesos-dns:
dig +short leader.mesos @$HOST | grep .
# for docker-registry:
curl -f http://$HOST:5000/v2/ | grep '{}'
# for my python processes
docker logs $(for i in $(docker ps -q --no-trunc); do docker inspect $i | grep
-sq MESOS_TASK_ID=${MESOS_TASK_ID:?} && echo $i; done) | grep 'Welcome to
interaction-indexer.'
# for rabbitmq
curl -f http://XX:XX@$HOST:15672/api/vhosts/YYYY | grep 'ZZZ'
{no-format}
> 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
> Fix For: 0.23.1, 0.24.1, 0.25.0
>
>
> 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)
