我不知道为什么以下请求不会在Marathon中开始运行状况检查。容器已启动，但状态仍为Deploying
{
"id": "bridged-webapp",
"cmd": "python3 -m http.server 8080",
"cpus": 0.1,
"mem": 64.0,
"instances": 1,
"container": {
"type": "DOCKER",
"docker": {
"image": "python:3",
"network": "BRIDGE",
"portMappings": [
{
"containerPort": 8080,
"hostPort": 31313,
"servicePort": 9000,
"protocol": "tcp"
}
]
}
},
"healthChecks": [
{
"protocol": "COMMAND",
"command": { "value": "echo 0" },
"maxConsecutiveFailures": 3
}
]
}
当我查看马拉松的日志时，它基本上只是说健康检查已经开始，但仅此而已:
Aug 28 16:52:33 cnode2 marathon[11495]: [2015-08-28 16:52:33,603] INFO Adding health check for app [/bridged-webapp] and version [2015-08-28T16:52:33.500Z]: [HealthCheck(Some(/),COMMAND,0,Some(Command(echo 0)),300 seconds,60 seconds,20 seconds,3,false)] (mesosphere.marathon.health.MarathonHealthCheckManager$$EnhancerByGuice$$d8828133:76)
Aug 28 16:52:33 cnode2 marathon[11495]: [INFO] [08/28/2015 16:52:33.604] [marathon-akka.actor.default-dispatcher-693] [akka://marathon/user/$kg] Starting health check actor for app [/bridged-webapp] and healthCheck [HealthCheck(Some(/),COMMAND,0,Some(Command(echo 0)),300 seconds,60 seconds,20 seconds,3,false)]
Aug 28 16:52:33 cnode2 marathon[11495]: [INFO] [08/28/2015 16:52:33.627] [marathon-akka.actor.default-dispatcher-694] [akka://marathon/user/MarathonScheduler/$a/DeploymentManager/4f3a1a8e-8934-441a-9c55-b7cf332893e2/$a] Successfully started 0 instances of /bridged-webapp
Aug 28 16:52:37 cnode2 marathon[11495]: [2015-08-28 16:52:37,080] INFO Received status update for task bridged-webapp.2f4399a5-4da5-11e5-b538-080027bb2503: TASK_RUNNING () (mesosphere.marathon.MarathonScheduler$$EnhancerByGuice$$b7a64e04:100)
在用户界面中，作业运行状况为灰色，表示运行状况检查未知。
真正奇怪的是，如果我运行相同的工作但没有容器，它将起作用。
有任何想法吗 ？
最佳答案
更新:
原来命令运行状况检查不适用于docker executor...。一位同事为此打开了一个问题:
https://github.com/mesosphere/marathon/issues/2140
我们至少将尽快更新文档。
感谢您发现这一点!
关于docker - 将Marathon Health Check与命令协议(protocol)和容器一起使用时的奇怪行为，我们在Stack Overflow上找到一个类似的问题：https://stackoverflow.com/questions/32276226/