--On Saturday, April 10, 2021 2:17 AM +0000 [email protected] wrote:
When I issue a write to provider 1 I see it send the update to provider2 and provider3. I then see provider2 and provider3 "syncprov_qresp: set up a new syncres mode=1" for each consumer that is connected to them (including the other provider that did not send the write). Provider 2 then sends a message to provider 3 that ignores it because "CSN too old, ignoring 20210410001522.122666Z#000000#065#000000 (reqStart=20210410001522.000001Z,cn=accesslog)". At the same time provider 3 sends a message to Provider 2 that gets ignored in the same way. Since it is expected that all consumers know about all providers it is perplexing to me why the providers "forward" the update along to its own known consumers. It seems this could be expected given my amateur ldap knowledge but I wanted to confirm because I don't immediately understand why that behavior is necessary (results in ignored messages).
Consumers are reading the accesslog and processing the updates they see there. So provider 3 and provider 2 each are reading the accesslog DB of provider 1. They each apply the change. Their consumers are reading their specific accesslogs and do the same. Since provider 3 is also reading the provider 2 accesslog, when it gets to the change it already received from provider 1, it discards it. Same concept for provider 2, when it discards the provider 1 change it finds in the provider 3 accesslog. Nothing is "forwarding" any updates.
--Quanah -- Quanah Gibson-Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: <http://www.symas.com>
