[
https://issues.apache.org/jira/browse/TS-3554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14547230#comment-14547230
]
Susan Hinrichs commented on TS-3554:
------------------------------------
I think I found at least the remaining memory leak. On reload,
SSLConfigParams::initialize is called which allocates the session_cache member
variable. Based on my analysis, the original value of the field is not freed.
Ultimately, we will likely only want to reinitialize the session table if the
relative parameters have changed. And probably put a reference count on the
data structures, so users of the original table do not start accessing bad data
when it is freed. [~briang] can you take a quick look and let me know if my
analysis seems right?
In the short term [~reveller] could you try setting
proxy.config.ssl.session_cache to 0 in records.config? This disables all
session caching, so this probably isn't great for a production environment, but
it would be useful for testing memory usage. As it stands, the code will still
allocate the base table on each reload (14KB), but no sessions should be
populated. I'll attach a patch that removes that allocation in the disabled
case too.
> ATS memory leak reloading ssl_multicert.config with many ssl cert configs
> -------------------------------------------------------------------------
>
> Key: TS-3554
> URL: https://issues.apache.org/jira/browse/TS-3554
> Project: Traffic Server
> Issue Type: Bug
> Components: Configuration, Core, SSL
> Reporter: Steven Feltner
> Assignee: Susan Hinrichs
> Fix For: 6.0.0
>
> Attachments: ts-3554-53-2.diff, ts-3554-53.diff
>
>
> ATS will consume all available memory on a server with 128GB of RAM.
> @shinrich suspects it may be due to CertLookup table not being freed on a
> config reload.
> Our current process:
> - New cert comes in
> - ssl_multicert.config and remap.config updated
> - traffic_line -x
> This reload could occur as often as every 3 mins with 5000+ certs configured.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
