点燃就绪探针 [英] Ignite ReadinessProbe

问题描述

在 Kubernetes 中部署 ignite 集群时，我遇到了阻止集群成员加入组的问题.如果我使用 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 上的 readinessProbe: spec.template.spec.container 具有防止 Kubernetes Pods 被列为相关 Kubernetes Service 作为 Endpoints

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)

然而，这会产生不希望的副作用，即在尚未准备好时暴露 Kubernetes Pod，因为 Spring 尚未完全启动......

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

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