How do you sync a "readonly database"? If all secondaries must contain the same data you must down them during update, obviously. So if one fails to update, all will remain down. Is that what you want? Maybe describe the scenario and requirements.
Kind regards, Ulrich Windl
-----Original Message----- From: alexey@filimonic.net alexey@filimonic.net Sent: Wednesday, February 12, 2025 12:37 PM To: openldap-technical@openldap.org Subject: [EXT] Few questions about replica (mirror mode?)
I plan few OpenLDAP servers: N readonly secondaries and single writable main.
In my case OpenLDAP is critical as readonly database, and changes are allowed to fail. But I need all readonly replicas contain the same data same time, and I have possibilities to temporarily disconnect readonly secondaries from master.
Is there a some kind of operational\replication mode when:
- Transactional changes over all servers:
Writable main fails writing to database and propagating them to secondaries in case any of secondaries can not receive same changes
- Secondary server may start "empty" and self-register as secondary server
on writeable main, then get in sync. Until sync complete, secondary server will not satisfy any requests from clients.