https://bugs.openldap.org/show_bug.cgi?id=9742
--- Comment #2 from Quanah Gibson-Mount quanah@openldap.org --- (In reply to Ondřej Kuzník from comment #1)
I guess running without that option wouldn't have helped and the same would have happened anyway since the log is just missing things.
Seems like adding a new serverID into a deltasync cluster is an administrative task that should be documented and managed. We have two options there:
- we have syncprov return a SYNC_REFRESH_REQUIRED, triggering a fallback
sync and tainting everyone's accesslog
- we mandate that the initial environment set up is done very carefully (the
seed is contacted first by everyone or distributed ahead of time) and keep the current behaviour
I consider it essential that it be trivial to add new nodes to an MPR cluster at any time w/o it requiring any special handling. Replication is already insanely complex in OpenLDAP.