[
https://issues.apache.org/jira/browse/TS-3642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alan M. Carroll reopened TS-3642:
---------------------------------
I've been reviewing this and I think this mainly swishes the dirt around.
The switched strings were obviously wrong but my testing shows that the overall
result is that the new settings are ignored, that is you must use the old
number `share_server_sessions` value to be effective.
The root cause is that the records management does not provide any indication
of whether the value is actually in records.config. For this reason if you
don't have `share_server_sessions` set, the internal logic will behave as if
you had it explicitly set to 2,overriding the new style values. This can't be
fixed by switching the order back for the same reason. Not sure what to do
about it, need to dig deeper.
Also, I found that SessionSharingMatchStrings is wrongly ordered which is
another problem.
> 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)
