[ 
https://issues.apache.org/jira/browse/TS-3554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14569259#comment-14569259
 ] 

ASF subversion and git services commented on TS-3554:
-----------------------------------------------------

Commit 258afd3479710bdbe55eca6a75d638c6fa0cb936 in trafficserver's branch 
refs/heads/5.3.x from shinrich
[ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=258afd3 ]

TS-3554:
  * Memory load reloading ssl_multicert.config.
  * Fix coverity discovered memory leak.
  * Another memory leak fix in the SSL cert loading. Specifically the ticket 
key blocks.
  * Had to rearrange functions so the test_certlookup program would link with 
additional release method.

(cherry picked from commit 98c87ee51b2ad91787b7a9fa2827cab1c03b3d22)
(cherry picked from commit 86a3a1464c32b24f02e2633906b93916f0080536)
(cherry picked from commit 88c5531b2dccbf2378b7e518aa946ddf5f88c72a)
(cherry picked from commit 29d72d393aa31950a173e43c26f0798efdc77127)


> 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: 5.3.1, 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)

Reply via email to