On May 6, 2022, at 09:22, Quanah Gibson-Mount quanah@fast-mail.org wrote:
--On Friday, May 6, 2022 9:55 AM -0700 Rallavagu Kon rallavagu@gmail.com wrote:
Hello All,
Running OpenLDAP version 2.4.58 on Ubuntu 20.04 in multicaster mode.
Under normal conditions, all operations perform normally in terms of replication consistency. However, when performing a stream of "ADD" operations eventually producer/consumer go out of sync where consumer thinks it has latest state than producer. All the write operations including ADD are pointed to a producer node (not load balancing the writes). Introduced 30 second delay to "ADD" operations (for the sake of testing) and experiencing the same behavior. The issue is manifesting after adding around 4k entries (sometimes even sooner).
I would note that OpenLDAP 2.4 series is no longer supported and that the OpenLDAP 2.5 series has numerous replication related changes. I'd strongly advise deploying OpenLDAP 2.5 and seeing if this resolves the issue.
If you are unable to package OpenLDAP 2.5 yourself, you may want to use the freely available from Symas or the LTB project.
Symas: https://repo.symas.com/soldap2.5/
LTB: https://ltb-project.org/download.html
Regards, Quanah
Upgraded to 2.5.12 and modified N-Way multi producer replication to “mirror mode”. Replication working fine after these changes. However, the monitoring scripts that were using ldapsearch are not able to read “contextCSN” attribute anymore. Hence, the monitoring is broken. However, slapcat output shows contextCSN attribute. Wondering if there is anything we need to look into.
Thanks in advance.