Issue 7433 - OpenLDAP 2.4.32 - possible memory leak at high load
Summary: OpenLDAP 2.4.32 - possible memory leak at high load
Status: VERIFIED FIXED
Alias: None
Product: OpenLDAP
Classification: Unclassified
Component: slapd (show other issues)
Version: 2.4.32
Hardware: All All
: --- normal
Target Milestone: ---
Assignee: OpenLDAP project
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-11-06 17:36 UTC by vb4607@att.com
Modified: 2017-04-13 15:22 UTC (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description vb4607@att.com 2012-11-06 17:36:42 UTC
Full_Name: Venkatesh Baglodi
Version:  2.4.32 
OS: Red Hat Enterprise Linux Server release 5.5
URL: ftp://ftp.openldap.org/incoming/
Submission from: (NULL) (139.76.64.65)


We have been facing frequent memory utilization issues with OpenLDAP 2.4.32 in
our production environment (multi-master mode, 6 servers), which requires
OpenLDAP server instances to be restarted almost every week. Utilization starts
at a lower percentage to start with (2-3%), but then gradually moves up and
never comes down. We have been using OpenLDAP 2.4.32 with hdb backend (BerkelyDB
v5.3.21) on Red Hat Enterprise Linux Server release 5.5 (Tikanga). Are there any
known issues with this version?
Comment 1 Quanah Gibson-Mount 2012-11-06 17:53:51 UTC
--On Tuesday, November 06, 2012 5:36 PM +0000 vb4607@att.com wrote:

> Full_Name: Venkatesh Baglodi
> Version:  2.4.32
> OS: Red Hat Enterprise Linux Server release 5.5
> URL: ftp://ftp.openldap.org/incoming/
> Submission from: (NULL) (139.76.64.65)
>
>
> We have been facing frequent memory utilization issues with OpenLDAP
> 2.4.32 in our production environment (multi-master mode, 6 servers),
> which requires OpenLDAP server instances to be restarted almost every
> week. Utilization starts at a lower percentage to start with (2-3%), but
> then gradually moves up and never comes down. We have been using OpenLDAP
> 2.4.32 with hdb backend (BerkelyDB v5.3.21) on Red Hat Enterprise Linux
> Server release 5.5 (Tikanga). Are there any known issues with this
> version?

Are you using the default glibc malloc, instead of tcmalloc?  That would be 
a common mistake that results in this sort of behavior.

--Quanah


--

Quanah Gibson-Mount
Sr. Member of Technical Staff
Zimbra, Inc
A Division of VMware, Inc.
--------------------
Zimbra ::  the leader in open source messaging and collaboration

Comment 2 OpenLDAP project 2017-04-13 15:22:34 UTC
no follow up, likely using glibc
Comment 3 Quanah Gibson-Mount 2017-04-13 15:22:34 UTC
changed notes
changed state Open to Closed