点燃准备探针 [英] Ignite ReadinessProbe

问题描述

在Kubernetes中部署一个点燃集群，我遇到了一个阻止集群成员加入该组的问题.如果我使用readinessProbe和livenessProbe，即使延迟低至10秒，它们的节点也不会彼此连接.如果我删除这些探针，它们会发现彼此很好.

Deploying an ignite cluster within Kubernetes, I cam across an issue that prevents cluster members from joining the group. If I use a readinessProbe and a livenessProbe, even with a delay as low as 10 seconds, they nodes never join each other. If I remove those probes, they find each other just fine.

所以，我的问题是:您可以使用这些探针来监视节点的运行状况吗?如果可以，什么是合适的设置?最重要的是，对Ignite进行快速健康检查将是什么好呢?

So, my question is: can you use these probes to monitor node health, and if so, what are appropriate settings. On top of that, what would be good, fast health checks for Ignite, anyway?

推荐答案

使用嵌入在Java spring应用程序中的Ignite，我面临着同样的问题.

I am facing the same issue, using Ignite embedded within a Java spring application.

正如您所说的那样，Kubernetes Deployment spec.template.spec.container上的readinessProbe:具有副作用，可以防止Kubernetes Pod在相关的Kubernetes Service上列为Endpoint s

As you said the readinessProbe: on the Kubernetes Deployment spec.template.spec.container has the side effect to prevent the Kubernetes Pods from being listed on the related Kubernetes Service as Endpoints

尝试不使用任何readinessProbe似乎确实更好(Ignite节点都加入了相同的Ignite群集)

Trying without any readinessProbe, it seems to indeed works better (Ignite nodes are all joinging the same Ignite cluster)

然而，这还具有不良的副作用，即由于Spring尚未完全启动，因此在尚未准备就绪时暴露Kubernetes Pod ...

Yet this have the undesired side effect of exposing the Kubernetes Pods when not yet ready, as Spring has not yet fully started ...

这篇关于点燃准备探针的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！