Yeah, that's a good question. We don't have TCP keep alive enabled (default
out-of-the-box setting in the core has them off too), that's something we could
try out as well, but, in my past experience tcp keep alives have caused other
weirdness. Does anyone have positive experience and recommend
Is ATS actually receiving FINs on those connections? Can ATS know the
session is dead before trying a transaction on it?
On Thu, Aug 15, 2019 at 7:45 PM Sudheer Vinukonda
wrote:
> Use case - We’ve some origins behind our proxy that get very low qps. Our
> server session sharing is set to Host ba
+1
I totally forgot to mention that making
`proxy.config.http.per_server.min_keep_alive_connections` overridable ensures
consistency and parity with the related configs
`proxy.config.http.per_server.connection.max` and
`proxy.config.http.per_server.connection.match` that are already overridabl
In addition to the bug Sudheer mentioned, it makes total sense to make the
config overridable on its own. It's a waste of connection resource to use a
global value of different origins.
Sudheer Vinukonda 于2019年8月15日周四
下午5:45写道：
> Use case - We’ve some origins behind our proxy that get very low q
Use case - We’ve some origins behind our proxy that get very low qps. Our
server session sharing is set to Host based and have a floor on min keep alive
connections as it is not overridable at the moment. Because of the floor the
server sessions never drop below that number, even when those indi
