Show Table of Contents
11.14. Trimming the Replication Changelog
The Directory Server changelog manages a list of received and processed changes. It includes changes clients run on the server and additionally directory changes from other replication partners. Changelog entries are removed only when both of the following conditions meet:
- The entry was successfully transferred to all replicas.
- The entry exceeded the time set in the
nsslapd-changelogmaxageparameter or the total number of records exceeded the value set innsslapd-changelogmaxentries. For further details, see the parameter descriptions in the Red Hat Directory Server Configuration, Command, and File Reference.
A record, including all subsequently created records, remains in the changelog until it is successfully replicated to all servers in the topology. This situation occurs, for example, if a Directory Server master was removed from the topology, but the replica update vector (RUV) has not been removed.
The file size of the changelog is not automatically reduced if you set a lower value in the
nsslapd-changelogmaxage or nsslapd-changelogmaxentries parameter. To recreate the changelog:
- Stop the Directory Server instance:
# service dirsrv stop instance_name
- Remove the changelog files:
# rm /var/lib/dirsrv/slapd-instance_name/changelogdb/*
- Start the instance:
# service dirsrv start instance_name
- Reinitialize the instance from an incoming replica. See Section 11.15, “Initializing Consumers”.
Where did the comment section go?
Red Hat's documentation publication system recently went through an upgrade to enable speedier, more mobile-friendly content. We decided to re-evaluate our commenting platform to ensure that it meets your expectations and serves as an optimal feedback mechanism. During this redesign, we invite your input on providing feedback on Red Hat documentation via the discussion platform.