tombstone entries
807573Nov 14 2002 — edited Nov 18 20021. On multi-masters (iDS5.1), it's understandable that deleted entries be kept (and marked with objectclass=nstombstone) for a while, because they may be used in conflict resolution situations. But why are they also replicated to the consumer servers ? Isn't that a waste of time and resources ?
2. When I manually (using ldapdelete) delete a tombstone entry on a master, the corresponding entry remains on all consumers (including the other master). So is the periodic purging done on each server independently ?
3. How do you change the purging interval or threshold ?
4. We are seeing the database files growing indefinitely. Could this be caused by a related purging bug ?