When creating a replica server, the replication changelog does not have a limit set(max entries or max age). The changelog should not be allowed to grow to an unlimited size, but instead some reasonable limit should be set, something like 7 days for max age:
dn: cn=changelog5,cn=config nsslapd-changelogmaxage: 7d
Setting a limit will help keep the changelog to reasonable size, and it will also help with the current improvements to the cleanallruv task (which will now be completely stripping the changelog of entries from invalid/cleaned rids). See:
https://fedorahosted.org/389/ticket/48208
Hello,
should be changelogmaxage attribute set during upgrade for existing replicas (is it safe?), or should be set it just for new replicas?
Replying to [comment:3 mbasti]:
Hello, should be changelogmaxage attribute set during upgrade for existing replicas (is it safe?), or should be set it just for new replicas?
The option can be set at any point, but sooner in the deployment the better. It is perfectly safe to set it on upgrades.
Thanks, Mark
Replying to [comment:4 mreynolds]:
Replying to [comment:3 mbasti]: Hello, should be changelogmaxage attribute set during upgrade for existing replicas (is it safe?), or should be set it just for new replicas? The option can be set at any point, but sooner in the deployment the better. It is perfectly safe to set it on upgrades. Thanks, Mark
Thank you!
FreeIPA 4.2.1 was released, moving to 4.2.x.
ipa-4-2:
master:
Metadata Update from @mreynolds: - Issue assigned to mbasti - Issue set to the milestone: FreeIPA 4.2.2
Login to comment on this ticket.