Bryan Call created TS-2422:
------------------------------
Summary: Add option to not attach the server session to the client
session
Key: TS-2422
URL: https://issues.apache.org/jira/browse/TS-2422
Project: Traffic Server
Issue Type: Improvement
Components: HTTP
Reporter: Bryan Call
By default traffic server will try to attach the server session to the client
session and not put it into the shared pool. Only if the client is not
keep-alive or server max connections is set or max origins is set will it place
the connection to the share pool.
I think we should remove the limiting connections logic and have a option to
directly control attaching server sessions to the client. Also, the option
should be off by default and connections should go into the shared pool by
default.
{code}
// If the client is still around, attach the server session
// to so the next ka request can use it. We bind privately to the
// client to add some degree of affinity to the system. However,
// we turn off private binding when outbound connections are being
// limit since it makes it too expensive to initiate a purge of idle
// server keep-alive sessions
if (ua_session && t_state.client_info.keep_alive == HTTP_KEEPALIVE &&
t_state.http_config_param->server_max_connections <= 0 &&
t_state.txn_conf->origin_max_connections <= 0) {
ua_session->attach_server_session(server_session);
} else {
{code}
--
This message was sent by Atlassian JIRA
(v6.1#6144)
