pjfanning commented on PR #1320: URL: https://github.com/apache/pekko-http/pull/1320#issuecomment-5887445630
The server-side equivalent (#1316) applies a jitter to the max connection age (`pekko.http.server.http2.max-connection-age-jitter`, default `0.1`, i.e. each connection is closed after 90%–110% of the configured age, same as grpc-java). Could this PR do the same on the client side, e.g. `pekko.http.client.http2.persistent-connection-max-age-jitter`? Without jitter, a fleet of clients that connected at roughly the same time (which is exactly the situation after a scale-out or rolling deployment) will all retire and reconnect at the same moment, causing a synchronized reconnect spike on the servers. With the retirement being break-before-make, it would also cause a correlated latency spike across the clients. It would be good to keep the client and server settings consistent in naming, semantics and validation (jitter `>= 0` and `< 1`, `0` disables it) with #1316. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
