Question

我在App Engine的项目中运行了几个Firebase-Queue NodeJS实例。

实例似乎一直在运行，在尝试GET请求后产生错误。

13:33:36.078
{"method":"GET","latencySeconds":"0.000","referer":"-","host":"-","user":"-","code":"502","remote":"130.211.0.96","agent":"GoogleHC/1.0","path":"/_ah/health","size":"166"}
13:33:36.421
{"method":"GET","latencySeconds":"0.000","referer":"-","host":"-","user":"-","code":"502","remote":"130.211.1.229","agent":"GoogleHC/1.0","path":"/_ah/health","size":"166"}

13:33:37.000
[error] 32#0: *80631 connect() failed (111: Connection refused) while connecting to upstream, client: 130.211.1.11, server: , request: "GET /_ah/health HTTP/1.1", upstream: "http://172.18.0.2:8080/_ah/health", host: "10.128.0.5"
13:33:37.000
[error] 32#0: *80633 connect() failed (111: Connection refused) while connecting to upstream, client: 130.211.3.85, server: , request: "GET /_ah/health HTTP/1.1", upstream: "http://172.18.0.2:8080/_ah/health", host: "10.128.0.5"

部署我的Node应用程序时，我的App.yaml文件如下所示：

runtime: nodejs
env: flex
service: album-queue
skip_files:
- ^(node_modules)

handlers:
- url: .*
  script: build/index.js

我认为它必须与它试图在内部进行的所有这些GET请求有关，但我不知道如何阻止它们/修复它。我的账单相当快地提高了，所以修理它＆gt; _＆lt;

非常好

Answer 1

App Engine Flex doesn't scale to zero就像标准环境一样。始终至少有一个实例在运行（默认实际为2）。您看到的请求是normal health checks。

App Engine节点灵活的实例不断运行

1 个答案: