+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 overridable for the same reasons that Zizhong mentions below. Also, to be clear `overridable` in the context of these settings only allows to override per Origin and not per Transaction (as the `per_server` in their naming indicates) as it doesn't make sense to make these transaction overridable. Thanks, Sudheer
https://docs.trafficserver.apache.org/en/latest/admin-guide/files/records.config.en.html#proxy-config-http-per-server-connection-max On Friday, August 16, 2019, 10:55:33 AM PDT, zzz <z...@apache.org> wrote: 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 <sudheervinuko...@yahoo.com.invalid> 于2019年8月15日周四 下午5:45写道： > 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 > individual servers are down or taken out of rotation. When a request > finally arrives for these services, because of host based match, we tend to > pick up these stale sessions, ignoring the new dns results. This can go on > for a while failing the requests. This is actually a bug in that we aren’t > purging the stale sessions (bcoz of the floor handling) from the session > pools. > > > So, we’d like to customise the floor min keep alive connections per > service. Here’s the PR https://github.com/apache/trafficserver/pull/5830 > > Any comments/suggestions? > > Thanks, > > Sudheer
