Update to gRPC logs GOAWAY with error code ENHANCE_YOUR_CALM messages
A number of us have seen these error logs spew in the console and now in /var/log/gitlab/puma/puma_stderr.log
:
E0118 05:01:33.447715294 4171522 chttp2_transport.cc:1111] Received a GOAWAY with error code ENHANCE_YOUR_CALM and debug data equal to "too_many_pings"
E0118 05:01:53.726215083 4171438 chttp2_transport.cc:1111] Received a GOAWAY with error code ENHANCE_YOUR_CALM and debug data equal to "too_many_pings"
E0118 05:12:55.915024893 4173110 chttp2_transport.cc:1111] Received a GOAWAY with error code ENHANCE_YOUR_CALM and debug data equal to "too_many_pings"
As far as I can tell, this isn't causing any issues, but https://grpc.github.io/grpc/core/md_doc_keepalive.html says:
- Why am I receiving a GOAWAY with error code ENHANCE_YOUR_CALM?
- A server sends a GOAWAY with ENHANCE_YOUR_CALM if the client sends too many misbehaving pings as described in A8-client-side-keepalive.md. Some scenarios where this can happen are -
- if a server has GRPC_ARG_KEEPALIVE_PERMIT_WITHOUT_CALLS set to false while the client has set this to true resulting in keepalive pings being sent even when there is no call in flight.
- if the client's GRPC_ARG_KEEPALIVE_TIME_MS setting is lower than the server's GRPC_ARG_HTTP2_MIN_RECV_PING_INTERVAL_WITHOUT_DATA_MS.
- A server sends a GOAWAY with ENHANCE_YOUR_CALM if the client sends too many misbehaving pings as described in A8-client-side-keepalive.md. Some scenarios where this can happen are -