[
https://issues.apache.org/jira/browse/TS-3554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14557311#comment-14557311
]
Susan Hinrichs commented on TS-3554:
------------------------------------
We narrowed it down to the version of the openssl library. I run with my own
build of the openssl library fetched from openssl.org. So the base
openssl-1.0.1e and openssl-1.0.1f do not show the unexpected memory growth.
However, the CentOS version of openssl-1.0.1e (which is base openssl-1.0.1e
plus a number of patches) does show the problem. By running with the yum
installed version of the openssl library or the rpmbuild source version of the
CentOS package, I am able to reproduce the memory growth on reload on my VM.
Need to do some more experiments to determine what in the patch is causing the
problem or if we move up to native 1.0.1m (the latest in the openssl version of
the 1.0.1 stream) does the problem go away.
> 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: limit_session_cache_alloc.diff, ts-3554-53-2.diff,
> ts-3554-53-3.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)
