[
https://issues.apache.org/jira/browse/TS-3642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14563943#comment-14563943
]
Sudheer Vinukonda commented on TS-3642:
---------------------------------------
A few notes:
*) I honestly don't understand the need to have a separate/new setting to
replace the existing *proxy.config.http.share_server_sessions*. The existing
setting has been working fine. It was indicated to me that the motivation
behind the change was TS-1893, but, reading through that jira, I haven't found
the need to change the *proxy.config.http.share_server_sessions* setting. That
jira, AFAICT asks for a configuration control on the *match* and not the
*pool*. Also, I am not sure, if it makes sense to remove the *disable* option
for the existing *share_server_sessions* and move it to the *match* setting.
*) Also, AFAICT, the new settings never worked until the coverity fix
a020cb2943f78f77ba8c928001359e8a2440cd28, which went in 5.3.0. Prior to that,
the old setting was always working (in 5.0.x/5.1.x/5.2.x) and has been active
in production. So, I'd argue that it is essential to preserve that behavior in
5.3.x at least.
> proxy.config.http.share_server_sessions not working
> ---------------------------------------------------
>
> Key: TS-3642
> URL: https://issues.apache.org/jira/browse/TS-3642
> Project: Traffic Server
> Issue Type: Bug
> Components: Configuration
> Affects Versions: 5.3.0
> Reporter: David Carlin
> Assignee: Sudheer Vinukonda
>
> Testing 5.3.0 and I noticed proxy.config.http.share_server_sessions = 1 no
> longer works. Saw a 10-15x increase in origin connections; there appears to
> be some reuse, I am seeing approximately 1.2-1.3 requests per origin
> connection.
> Setting "proxy.config.http.server_session_sharing.pool = global" restored
> expected behavior (Thanks [~sudheerv]!)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
