[
https://issues.apache.org/jira/browse/TS-3554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14557327#comment-14557327
]
Susan Hinrichs commented on TS-3554:
------------------------------------
More data from my VM
Version openssl compiled/run against => Status
1.0.1e from openssl.org => No memory growth
1.0.1m from openssl.org => No memory growth
1.0.1e provided by yum Centos6.4 (30.el6.8) => Memory growth. Cannot even load
base 3K line ssl_multicert without extra traffic_cop time delay
1.0.1e build from Centos (30.el6.8) source rpm => Same behavior as yum version
1.0.2 from openssl.org => No memory growth
Not clear what the centos patches are trying to provide beyond the 1.0.1m
version (the latest in the 1.0.1 series provided by openssl, updated March 19,
2015)
> 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)
