Univention Bugzilla – Bug 47339
Downsize transaction file automatically
Last modified: 2021-05-14 16:50:54 CEST
/var/lib/univention-ldap/notify can become quite large in larger environments, especially UCS@school multi server scenarios which slows down the join process of new UCS systems. Therefore, we should downsize the transaction file automatically (check the replication status in the domain, cut to the last successfully replicated transaction plus buffer). This would make https://help.univention.com/t/downsizing-transaction-file/6434 obsolete.
All UCS systems running UDL could write their /var/lib/univention-directory-listener/notifier_id to their LDAP machine account on a regular basis (daily/weekly). Then all transactions before min(...) can be dropped. A Nagios or UMC-diagnostics module can check for systems far behind and notify the admin about this systems: "The system XXX was inactive for time YYY now. It last reported listener transaction ID ZZZ, which is far behind the current AAA. This prevents truncating the transaction file. You should delete the machine account if the system is longer active." This might be problematic if snapshots are used and only a single system is reset. If the transaction file is shortened too much, all older systems must be re-joined. Truncating the file is not enough as since UCS-4.3 erratum 427 the transactions are not only written to /var/lib/univention-ldap/notify/transaction, but also to cn=translog.
should be still relevant for UCS 4.4