https://bugs.openldap.org/show_bug.cgi?id=8179
--- Comment #1 from Leonardo Lopes <[email protected]> --- Hello. I can't say if this is really a bug, but this is one of the (very) few results I could find while serching the internet for MDB_MAP_RESIZED error in OpenLDAP. I'll describe my setup and the circumstances of the error. I have OpenLDAP/LMDB installed from Debian 10 default packages in a amd64 box. The package versions are: - liblmdb: 0.9.22-1 - slapd: 2.4.47 Along with the usual settings, I chose the mdb backend with maxsize = 7516192768 (7GB). The on-disk base size (the data.mdb file) is 134MB. I also have loglevel = stats Everything seems to work flawless and fast, so all of sudden syslog prints the this message: Apr 9 15:06:09 vm-ldap-01 slapd[12826]: mdb_opinfo_get: err MDB_MAP_RESIZED: Database contents grew beyond environment mapsize(-30785) and seconds later, the slapd daemon stop to answer all requests. For the record, my workload is essentially reads with ~1000k SRCH ops, ~750k BIND ops and only ~100 ADD/DEL/MOD ops in a typical day. I tried to relate the error with anything possible, but no success. All I have is that when the error occurs, there were always an ADD operation logged right before. As I said, search the internet were of almost no help, except for this bug report and for the source code. After read the sources and the context of occurrence for the MDB_MAP_RESIZED error, I thought it may really be a bug. Thanks for your consideration. -- You are receiving this mail because: You are on the CC list for the issue.
