Hello,
we had a long-running (several days) process doing add and modify operations in OpenLDAP 2.4.41 + LMDB backend + SLES 11.3.
When the process was stopped, we experienced minutes of intensive disk write by LMDB.
The LMDB option dbnosync is not set.
Checking git we see that there should be a transaction commit in LMDB after every LDAP add/modify operation, and the updating of on-disk contents should happen after each LDAP add/modify operation.
Furthermore, at the OS level, dirty pages should be generally flushed every 5 seconds.
So we wonder what could possibly cause such a significant I/O burst?
Regards,
tamas
--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 over 4 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
openldap-technical@openldap.org