On Mon, Jul 20, 2020 at 08:49:51AM +0200, Ulrich Windl wrote: > Quanah Gibson-Mount <[email protected]> schrieb am 16.07.2020 um 17:01 in > Nachricht <33146DC712C0F6197C97C784@[192.168.0.156]>: >> I've referenced the underlying bug for years. ITS#8125. > > I read the bug, but it's not quite clear what the true reason is. for me I > got: modrdn operations, multi-valued attributes with more than one change per > second, possibly non-persistent sessionlog. This combination leads to > unreliable synchronization.
The situation is when several providers try and do a complete resync with each other at the same time. That situation is not handled well. Usually you have several layers before that (deltasync, sessionlog, yet more stuff in 2.5) that are well tested. > And it seems the bug isn't fixed yet. No and there is no way to fix this in 2.4. We're aiming to fix this in 2.5 but aren't there yet. > Couldn't there be a warning at least saying something like "unsafe sync > configuration detected. Expüect inconsistent replica"? The problem only surfaces when two servers get into the same situation at the same time, hard to detect. With multiple providers, you want to use deltasync at this point. Regards, -- Ondřej Kuzník Senior Software Engineer Symas Corporation http://www.symas.com Packaged, certified, and supported LDAP solutions powered by OpenLDAP
