Hi Thierry, thanks for your reply, regarding your questions: > > Did you also see some logs like "lcache_load_buffer - Can't load changelog buffer starting at CSN...' ? No, I have checked the current error logs of both suppliers (and the supplier in our lab environment) and those messages don't show up. > > Did you dump the changelog with dbscan ? No, I dumped the changelog with: dsconf slapd-mdir01 replication export-changelog default -r "dc=domain,dc=net" I tried your command, but we are using mdb as the database backend so it can't read the data.mdb file. > > Did you identify a reproducible testcase? (size of the DB, number of update, How long did it happen after the topology was setup...) Not yet, I will try to recreate our setup and will come back to you > > size of the DB For Prod, around 9 GB For Lab, around 300 MB > > number of update During peak around 280 - 320 per hour, add and delete each. It is worth mentioning that the provisioning system is not able to send updates, in case a change happens on an existing entry it sends a delete and an add. So combined it's 560 - 640 writes per hour. The 2 changes happen during the same connection. The provisioning system opens a new connection for each change. > > How long did it happen after the topology was setup. Unfortunately I can't answer this concretely. I was first informed about those errors beginning of June. The new environment went live beginning of April. Kind regards, Florian -- _______________________________________________ 389-users mailing list -- 389-users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to 389-users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/389-users@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
