Sometimes it happen the consumer go out of sync. Convenient solution:What you describe is not a database out of sync, but a corrupted database. You never have to delete a database that is out of sync; you'll just have to refresh it, and that should be automatic if configured and working correctly
Except, as is often the case, you're generally wrong. Unfortunately, every release prior to 2.4.44 definitely has cases where DBs can go out of sync. And even worse, resyncing will *not* necessarily get them back in sync. So often you *do* have to delete a database that is out of sync, and load it with a slapcat from the master. As I've often noted, the form of replication *least likely* to run into this is delta-syncrepl. Hopefully with 2.4.44 all known cases of this are addressed, but that still is not guaranteed.
* <http://www.openldap.org/its/index.cgi/?findid=8281> * <http://www.openldap.org/its/index.cgi/?findid=8365> --Quanah -- Quanah Gibson-Mount Platform Architect Zimbra, Inc. -------------------- Zimbra :: the leader in open source messaging and collaboration A division of Synacor, Inc