On Wed, Jun 26, 2019 at 07:41:27PM +0200, Michael Würtinger wrote:
we're running a gRPC service behind an NGINX load balancer and we often see that the connection gets shut down with a GOAWAY message. Since our request deadlines are quite small and it takes some time to re-establish a connection this often leads to many failed requests.
After analyzing the situation we realized that it is caused by the "http2_max_requests" option which defaults to 1000. After setting this to a ridiculously high value our problems disappeared.
While there probably are use cases where limiting the life time of a connection makes sense we were wondering why it is not possible to disable this functionality and let a connection just live as long as possible?
The following patch allows to do just that by setting http2_max_requests to 0.
No, thank you. Closing connections periodically is required to free associated memory, and shouldn't be disabled.