On 6/17/21 2:11 PM, Marco Favero wrote:
Ah, I don't have RA rh5-->dr-rh1. So, I could setup a RA from all multimaster to dr-rh1 to avoid this kind of problems. I'm not sure to understand. Really, I have a real time RA from rh5 to rh1, and from rh1 to rh5. So, if I initialize rh1 from rh5, rh1 should still replicates to dr-rh1, because rh5 is always in synch with rh1...
Administrative task are sensitive and some side effect can impact replication. When you reinit rh5->rh1, then rh1 can still replicates to dr-rh1. However a side effect of reinit is that it clears the changelog of rh1. So if dr-rh1 is late, then rh1 having lost history of old updates (changelog reset) is able to connect to dr-rh1 but is no longer able to find in its cleared changelog, the old update it should start replication from.
The workaround is to give rh5 a chance to directly update dr-rh1. thanks thierry
Thank you Marco _______________________________________________ 389-users mailing list -- 389-users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to 389-users-leave@xxxxxxxxxxxxxxxxxxxxxxx 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@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
_______________________________________________ 389-users mailing list -- 389-users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to 389-users-leave@xxxxxxxxxxxxxxxxxxxxxxx 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@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
