Google App Engine 健康检查垃圾邮件应用 [英] Google App Engine health checks spamming app

问题描述

我已经使用以下 app.yaml 配置部署了一个在 Google App Engine Flex 运行时上运行的 nodejs 应用:

运行时:nodejs环境:弹性健康检查:enable_health_check: 真check_interval_sec: 20超时秒:4不健康阈值:2健康阈值:2

根据

知道为什么会这样吗?

解决方案

很遗憾，我们的文档似乎存在错误.今天，确实，应用程序确实经常进行健康检查.

原因是多方面的，但一般来说，每个 VM 都会在您指定的重复间隔(默认情况下，非常激进，1 秒)接受 3 * 2 次不同的健康检查.这样做的原因是 2 种类型的运行状况检查(自动修复程序和 LB 的)，并且出于可用性原因各 3 种.

话虽如此，我们目前正在研究一种新的健康检查形式，该形式将很快发布，并应该解决现有健康检查行为的这一问题和其他问题(至少使默认设置更易于管理并提供更多调整选项给用户).

敬请期待！

I've deployed a nodejs app running on the Google App Engine Flex runtime using the following app.yaml configuration:

runtime: nodejs
env: flex
health_check:
  enable_health_check: True
  check_interval_sec: 20
  timeout_sec: 4
  unhealthy_threshold: 2
  healthy_threshold: 2

According to the health check documentation the health checks should hit the /_ah/health endpoint every 20 seconds. However I noticed that my app is getting spammed with these health checks multiple times per second, even though the app responds with 200 status code:

Any idea why this is happening?

解决方案

Unfortunately it does seem like we have a bug on our docs. Today, indeed, apps do get health checked on a pretty frequent basis.

The reason is many fold, but in general each VM will be hit by 3 * 2 different health checks at the recurrence interval you specify (by default, the, very aggressive, 1 sec). The reason for this is 2 types of health check (autohealer and LB ones) and 3 of each for availability reasons.

That being said, we are currently working on a new shape of health checks that will be released pretty soon and should fix this and other problems with the existing health checking behavior (at least make the defaults more manageable and giving more tuning options to users).

Stay tuned!

这篇关于Google App Engine 健康检查垃圾邮件应用的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！