You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@trafficserver.apache.org by "Leif Hedstrom (JIRA)" <ji...@apache.org> on 2013/08/05 22:44:48 UTC

[jira] [Updated] (TS-2098) Memory leak with reloading SSL certificates 3.3.4

     [ https://issues.apache.org/jira/browse/TS-2098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Leif Hedstrom updated TS-2098:
------------------------------

    Fix Version/s: 3.3.5
    
> Memory leak with reloading SSL certificates 3.3.4
> -------------------------------------------------
>
>                 Key: TS-2098
>                 URL: https://issues.apache.org/jira/browse/TS-2098
>             Project: Traffic Server
>          Issue Type: Bug
>          Components: SSL
>            Reporter: Kris Lindgren
>             Fix For: 3.3.5
>
>
> When using the new feature of 3.3.4 to re-read the ssl configuration without restart the old memory that the configuration uses is not released.
> I have ~220k ssl certs defined which consumes ~1.2gb of memory.  If I add/remove a single ssl cert from ssl_multicert.config and reload via traffic_line -x memory usage increases from 1.2gb to 2.4gb and stays there.  If I make another change and reload again via traffic_line -x, memory usage jumps to 3.6gb and stays there.
> It appears that after successfully loading the new configuration into memory the old configuration is never purged.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira