[ 
https://issues.apache.org/jira/browse/TS-312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13841917#comment-13841917
 ] 

Bryan Call commented on TS-312:
-------------------------------

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}

> add option to always share keep-alive connections to the origin server 
> -----------------------------------------------------------------------
>
>                 Key: TS-312
>                 URL: https://issues.apache.org/jira/browse/TS-312
>             Project: Traffic Server
>          Issue Type: Improvement
>          Components: Network
>            Reporter: Miles Libbey
>            Assignee: Bryan Call
>            Priority: Minor
>
> (was yahoo bug 1411758)
> Original description
> by Bryan Call (bcall) 2 years ago at 2007-08-08 13:35
> Leif and I were talking about extending the meaning of 
> proxy.config.http.share_server_session for reusing keep-alive connections 
> from the TS server and the origin server, for separate clients attached to 
> TS.  You can read more about this in
> [BUG 1162233].  The configuration options should be:
> so lets add more "options" to share_server_session? E.g.
> 0 - Never share/reuse connections
> 1 - Share/reuse connections if max_connections is set (default)
> 2 - Always try to share-reuse connections
> option 1 will give the behavior we currently have and 2 will always try to 
> share the keep-alive connections to the
> origin servers.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Reply via email to