[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: Intensive disk write after long-running LDAP activity terminated

To: Tamás Rébeli-Szabó <tamas.rebeli.szabo@webvalto.hu>, openldap-technical@openldap.org
Subject: Re: Intensive disk write after long-running LDAP activity terminated
From: Quanah Gibson-Mount <quanah@symas.com>
Date: Mon, 22 Jul 2019 06:25:37 -0700
Content-disposition: inline
In-reply-to: <CA+QQuRgy9kZ_PPjRfz9cnt4dEycGEfsxCGRAD4wr2Z5nwMQBeA@mail.gmail.com>
References: <CA+QQuRgy9kZ_PPjRfz9cnt4dEycGEfsxCGRAD4wr2Z5nwMQBeA@mail.gmail.com>

--On Monday, July 22, 2019 2:20 PM +0200 Tamás Rébeli-Szabó<tamas.rebeli.szabo@webvalto.hu> wrote:




Hello,

we had a long-running (several days) process doing add and modify
operations in OpenLDAP 2.4.41 + LMDB backend + SLES 11.3.

I would note you're talking about OpenLDAP and LMDB releases that are over4 years old, past which point numerous issues have been fixed for both.


LMDB 0.9.15 Release (2015/06/19)
OpenLDAP 2.4.41 Release (2015/06/21)

--Quanah



--

Quanah Gibson-Mount
Product Architect
Symas Corporation
Packaged, certified, and supported LDAP solutions powered by OpenLDAP:
<http://www.symas.com>

References:
- Intensive disk write after long-running LDAP activity terminated
  - From: Tamás Rébeli-Szabó <tamas.rebeli.szabo@webvalto.hu>

Prev by Date: Intensive disk write after long-running LDAP activity terminated
Next by Date: Re: where is debuglevel documented ?
Index(es):
- Chronological
- Thread