https://bugs.openldap.org/show_bug.cgi?id=9341
--- Comment #2 from Ondřej Kuzník <[email protected]> --- At the moment getting a good/stable resolution is also compounded by the fact there is an additional ordering - timestamp of the CSNs themselves which might or might not match the order they arrive in each consumer. The only thing we can guarantee is that if CSN a < CSN b apply to the same entry and both share the same serverId, they will arrive in order a, then b or a somehow "combined" operation with the CSN of b. -- You are receiving this mail because: You are on the CC list for the issue.
