You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to Google App Engine
Hey,
When i connect to the docker container of my instance i see about 10 health checks/second:
130.211.1.74 - - [19/May/2018:08:36:11 +0000] "GET /_ah/health HTTP/1.1" 200 2346 "-" "GoogleHC/1.0" tracecontext="-" timestampSeconds="1526718971.027000000" latencySeconds="0.004" x-forwarded-for="-" appLatencySeconds="0.004" appStatusCode="200" upgrade="-" iap_jwt_action="noop_off" 130.211.1.80 - - [19/May/2018:08:36:11 +0000] "GET /_ah/health HTTP/1.1" 200 2346 "-" "GoogleHC/1.0" tracecontext="-" timestampSeconds="1526718971.234000000" latencySeconds="0.003" x-forwarded-for="-" appLatencySeconds="0.003" appStatusCode="200" upgrade="-" iap_jwt_action="noop_off" 130.211.1.80 - - [19/May/2018:08:36:11 +0000] "GET /_ah/health HTTP/1.1" 200 2346 "-" "GoogleHC/1.0" tracecontext="-" timestampSeconds="1526718971.236000000" latencySeconds="0.005" x-forwarded-for="-" appLatencySeconds="0.005" appStatusCode="200" upgrade="-" iap_jwt_action="noop_off" 130.211.1.74 - - [19/May/2018:08:36:11 +0000] "GET /_ah/health HTTP/1.1" 200 2346 "-" "GoogleHC/1.0" tracecontext="-" timestampSeconds="1526718971.340000000" latencySeconds="0.031" x-forwarded-for="-" appLatencySeconds="0.031" appStatusCode="200" upgrade="-" iap_jwt_action="noop_off" 130.211.1.82 - - [19/May/2018:08:36:11 +0000] "GET /_ah/health HTTP/1.1" 200 2346 "-" "GoogleHC/1.0" tracecontext="-" timestampSeconds="1526718971.604000000" latencySeconds="0.002" x-forwarded-for="-" appLatencySeconds="0.002" appStatusCode="200" upgrade="-" iap_jwt_action="noop_off" 130.211.1.83 - - [19/May/2018:08:36:11 +0000] "GET /_ah/health HTTP/1.1" 200 2346 "-" "GoogleHC/1.0" tracecontext="-" timestampSeconds="1526718971.680000000" latencySeconds="0.002" x-forwarded-for="-" appLatencySeconds="0.002" appStatusCode="200" upgrade="-" iap_jwt_action="noop_off" 130.211.1.83 - - [19/May/2018:08:36:11 +0000] "GET /_ah/health HTTP/1.1" 200 2346 "-" "GoogleHC/1.0" tracecontext="-" timestampSeconds="1526718971.681000000" latencySeconds="0.003" x-forwarded-for="-" appLatencySeconds="0.003" appStatusCode="200" upgrade="-" iap_jwt_action="noop_off" 130.211.1.82 - - [19/May/2018:08:36:11 +0000] "GET /_ah/health HTTP/1.1" 200 2346 "-" "GoogleHC/1.0" tracecontext="-" timestampSeconds="1526718971.708000000" latencySeconds="0.075" x-forwarded-for="-" appLatencySeconds="0.075" appStatusCode="200" upgrade="-" iap_jwt_action="noop_off" 130.211.3.50 - - [19/May/2018:08:36:11 +0000] "GET /_ah/health HTTP/1.1" 200 2346 "-" "GoogleHC/1.0" tracecontext="-" timestampSeconds="1526718971.816000000" latencySeconds="0.041" x-forwarded-for="-" appLatencySeconds="0.041" appStatusCode="200" upgrade="-" iap_jwt_action="noop_off" 130.211.3.50 - - [19/May/2018:08:36:11 +0000] "GET /_ah/health HTTP/1.1" 200 2346 "-" "GoogleHC/1.0" tracecontext="-" timestampSeconds="1526718971.921000000" latencySeconds="0.028" x-forwarded-for="-" appLatencySeconds="0.028" appStatusCode="200" upgrade="-" iap_jwt_action="noop_off" How can i disable this? It does not seem too normal does it?If i try to set health checks parameters in the app.yaml file i get: ERROR: (gcloud.app.deploy) INVALID_ARGUMENT: App Engine flexible environment does not support changing health check types with in place deployments. Please remove the 'liveness_check' and/or 'readiness_check' section from your app.yaml.
Kenworth (Google Cloud Platform)
unread,
May 20, 2018, 1:25:35 PM5/20/18
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to Google App Engine
Hi Valerio, a thread like this is off-topic for Google Groups. As it may potentially be a defect on the platform and most likely lead to a specific situation which may require some exchange of project information to reproduce the behavior you described, I highly encourage you to submit a defect report as described in this article so that proper attention and weight will be given to it. We monitor that issue tracker closely.