> On Apr 10, 2019, at 9:34 AM, ezko <[email protected]> wrote:
>
> Actually we missed that one.
> looks much better now.
> thanks very much for the catch.
Great. Just as an FYI, we changed how we manage connections in 7.x.
Essentially, proxy.config.net.connections_throttle is the max number of
connections it can handle, and it should be at least as big as
proxy.config.net.max_connections_in. However, the latter also has an
implication on how we reap idle connections.
In old versions of ATS, idle connections (“Keep-Alive”) would time out via
server settings. But now, we instead try to keep them around as long as
possible (or until the client closes it), *unless* you reach
proxy.config.net.max_connections_in, at which point we start killing the
oldest, idle connection.
I think this new system is a lot better, and easier to manage, since you don’t
have to try to guess the KA timeouts on the server to match up your max
connection settings. It’s a lot more robust this way, but perhaps slightly
confusing in that there are two settings.
Bryan: I’m wondering if we should make something less confusing here? Should we
have something such that proxy.config.net.connections_throttle is replaced with
the “sum” of the max incoming and outgoing server (plus some additional
futzing) ? We already have proxy.config.http.server_max_connections, which is
default to zero now, but maybe it should be set to 30k as well, and we tune the
max number of FDs to (proxy.config.http.server_max_connections +
proxy.config.net.max_connections_in) ?
Cheers,
— leif
>
> BR,
> Erez
>
>
>
>
> --
> Sent from: http://apache-traffic-server.24303.n7.nabble.com/
