大叔经验分享(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;
---------------------------------------------------------------- 结束啦,我是大魔王先生的分割线 :) ----------------------------------------------------------------
- 由于大魔王先生能力有限,文中可能存在错误,欢迎指正、补充!
- 感谢您的阅读,如果文章对您有用,那么请为大魔王先生轻轻点个赞,ありがとう