15.13. Managing Deleted Entries with Replication
nsDS5ReplicaTombstonePurgeIntervalattribute); the purge removes old tombstone entries. Tombstone entries are saved for a given amount of time (set in the
nsDS5ReplicaPurgeDelayattribute); once a tombstone entry is older than the delay period, it is reaped at the next purge job.
,cn=mapping tree,cn=configconfiguration entry. There are two considerations when defining the purge settings for replication:
- The purge operation is time-consuming, especially if the server handles a lot of delete operations. Do not set the purge interval too low or it could consume too many server resources and affect performance.
- Suppliers use change information, including tombstone entries, to prime replication after initialization. There should be enough of a backlog of changes to effectively re-initialize consumers and to resolve replication conflicts. Do not set the purge delay (the age of tombstone entries) too low or you could lose information required to resolve replication conflicts.Set the purge delay so that it is slightly longer than the longest replication schedule in the replication topology. For example, if the longest replication interval is 24 hours, keep tombstone entries around for 25 hours. This ensures that there is enough change history to initialize consumers and prevent the data stored in different suppliers from diverging.
# ldapmodify -D "cn=Directory Manager" -W -x -h supplier1.example.com dn: cn=replica,cn=dc\=example\,dc\=com,cn=mapping tree,cn=config changetype: modify replace: nsDS5ReplicaTombstonePurgeInterval nsDS5ReplicaTombstonePurgeInterval: 43200 # in seconds, 12 hours - changetype: modify replace: nsDS5ReplicaPurgeDelay nsDS5ReplicaPurgeDelay: 90000 # in seconds, 25 hours
nsDS5ReplicaPurgeDelayattributes. Both attributes have values set in seconds, so the purge operations can be initiated almost immediately.