启动Ditto服务后，pods会从"OK“切换到"Liveness failed”或"Readiness failed“

Question

按照README.txt文件中提供的说明，我设法在minikube上启动并运行了Ditto。我必须对.yaml文件(参见Deployment of Ditto and MongoDB using kubectl fails because of unsupported version "extensions/v1beta1")做一些细微的调整。

现在Ditto服务已经启动，pods从状态"OK“切换到以下错误：

pod connectivity: Liveness probe failed: Get "http://172.17.0.6:8558/alive": context deadline exceeded (Client.Timeout exceeded while awaiting headers)

pod gateway: Readiness probe failed: Get "http://172.17.0.9:8558/ready": context deadline exceeded (Client.Timeout exceeded while awaiting headers)

pod things: Readiness probe failed: Get "http://172.17.0.5:8558/ready": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
Back-off restarting failed container

pod things-search: Readiness probe failed: Get "http://172.17.0.8:8558/ready": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
Back-off restarting failed container

pod policies: Readiness probe failed: Get "http://172.17.0.7:8558/ready": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
Back-off restarting failed container

pod concierge: Readiness probe failed: Get "http://172.17.0.4:8558/ready": context deadline exceeded (Client.Timeout exceeded while awaiting headers)

即使所有pod的状态都是"OK"，我也无法发送POST请求而不收到错误502 (Bad Gateway)。

任何对解决这个问题的帮助都是非常感谢的。

提前谢谢你。

Answer 1

也许这是由Minikube VM的资源问题引起的。虚拟机有多少个CPU和内存？也许你可以扩展资源，然后再试一次？

Answer 2

我在docker中运行Ditto时遇到了几个问题，直到我将docker中的CPU使用率从4改为8。

Docker Settings

由于我使用的是4Core/8Thread，我想知道设置为4是否会导致使用2个内核(在旧mac上)。这对Ditto来说似乎太少了。

托马斯