On Thu, Nov 16, 2023, at 12:54 PM, William Faulk wrote: > > > Ultimately, I think I mostly understand now. A change happens on a replica, > it assigns a CSN to it and updates its RUV to indicate that that's now the > newest CSN it has. Then a replication event occurs with its peers and those > peers basically say "you have something newer; send me everything you > originated after this last CSN from you that I know about". And then a > replication event happens to their peers and they see that there's something > new from that replica, etc.
Kind of, but it's the other way around: the supplier server with the new changes connects to a peer server and retrieves its ruv. From that it decides which of the changes it should to send. The consumer server doesn't ask for anything directly. The process is supplier-initiated.
-- _______________________________________________ 389-users mailing list -- 389-users@lists.fedoraproject.org To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
