Univention Bugzilla – Bug 56954
Ignore temporary objects during join
Last modified: 2024-01-24 15:15:52 CET
With Bug #48626, we stopped replicating temporary locking objects during replication, since they are not needed anywhere but on the primary. During the initial join of a server, though the temporary objects are still replicated to the joining server. I've seen customers have ~200.000 of those, because they were abandoned at some time by UDM. After deleting them, the initial join of a school server was ~5 hours faster than before. We should ignore them during the initial join, to decrease the load of joining servers.
1cc97110191 | Don't replicate objectClass=lock 4d013220acb | Update documentation Package: univention-directory-replication Version: 13.0.8-2 Branch: ucs_5.0-0 Scope: errata5.0-6 Package: univention-directory-logger Version: 11.0.5-2 Branch: ucs_5.0-0 Scope: errata5.0-6 Package: univention-ad-connector Version: 14.0.17-2 Branch: ucs_5.0-0 Scope: errata5.0-6 Package: univention-s4-connector Version: 14.0.16-2 Branch: ucs_5.0-0 Scope: errata5.0-6
OK: YAML OK: installation OK: objectClass=lock objects are not replicated during the initial join (with s4-connector, ad-connector , directory-logger installed OK: Jenkins Verified
<https://errata.software-univention.de/#/?erratum=5.0x920> <https://errata.software-univention.de/#/?erratum=5.0x921> <https://errata.software-univention.de/#/?erratum=5.0x922> <https://errata.software-univention.de/#/?erratum=5.0x923>