【原创】大叔经验分享（70）marathon重启app后一直处于waiting状态

提示：扫一扫查出行
【扫一扫了解最新限行尾号】
复制提示

marathon重启app后一直处于waiting状态，查看marathon日志

# journalctl -u marathon -f

有如下日志：

Jun 14 12:58:38 DataOne-002 marathon[15801]: [2019-06-14 12:58:38,321] INFO Offer [2a0fb98b-f8df-44e8-965c-54ad7203fa45-O1623]. Constraints for run spec [/app] not satisfied.
Jun 14 12:58:38 DataOne-002 marathon[15801]: The conflicting constraints are: [field: "hostname"
Jun 14 12:58:38 DataOne-002 marathon[15801]: operator: CLUSTER
Jun 14 12:58:38 DataOne-002 marathon[15801]: value: "192.168.0.1"
Jun 14 12:58:38 DataOne-002 marathon[15801]: ] (mesosphere.mesos.ResourceMatcher$:marathon-akka.actor.default-dispatcher-3645)
Jun 14 12:58:38 DataOne-002 marathon[15801]: [2019-06-14 12:58:38,322] INFO Offer [2a0fb98b-f8df-44e8-965c-54ad7203fa45-O1624]. Considering resources with roles {*} without resident reservation labels. Not all basic resources satisfied: cpus NOT SATISFIED (1.0 > 0.0), mem SATISFIED (1024.0 <= 1024.0) (mesosphere.mesos.ResourceMatcher$:marathon-akka.actor.default-dispatcher-3645)

可见是由于资源一直没有满足，上例中为cpu资源不足，所以无法deploy；