Is there a way reliable determine whether ldap slave is sync with master? Currently i am using ContextCSN diff between master and slave to determine the lag.
Thanks in advance.
Ashok
On Fri, Jul 12, 2013 at 9:26 PM, Quanah Gibson-Mount quanah@zimbra.comwrote:
--On Friday, July 12, 2013 5:40 PM +0530 Ashok ashok.shah@flipkart.com wrote:
Hi,
I am running ldap master and multiple slave with RefreshandPersist config. ldap search for an user shows different set of records. ContextCSN on master and slave are exactly same. What can i do to fix this. I tried restarting slave ldap but didn't help. Also i keep getting do_syncrepl: rid=112 rc 68 retrying every minute. I doubt if there is replication issue.
It sounds like it is resyncing the DB, and skipping entries that already exist: LDAP_ALREADY_EXISTS is error code 68.
--Quanah
--
Quanah Gibson-Mount Sr. Member of Technical Staff Zimbra, Inc A Division of VMware, Inc.
Zimbra :: the leader in open source messaging and collaboration
Is there a way to reliable determine whether ldap slave is in sync with master? Currently i am using ContextCSN diff between master and slave to determine the lag.
Thanks in advance.
Thanks, Ashok On Fri, Jul 12, 2013 at 10:36 PM, Ashok Kumar Shah ashok.shah@flipkart.comwrote:
Is there a way reliable determine whether ldap slave is sync with master? Currently i am using ContextCSN diff between master and slave to determine the lag.
Thanks in advance.
Ashok
On Fri, Jul 12, 2013 at 9:26 PM, Quanah Gibson-Mount quanah@zimbra.comwrote:
--On Friday, July 12, 2013 5:40 PM +0530 Ashok ashok.shah@flipkart.com wrote:
Hi,
I am running ldap master and multiple slave with RefreshandPersist config. ldap search for an user shows different set of records. ContextCSN on master and slave are exactly same. What can i do to fix this. I tried restarting slave ldap but didn't help. Also i keep getting do_syncrepl: rid=112 rc 68 retrying every minute. I doubt if there is replication issue.
It sounds like it is resyncing the DB, and skipping entries that already exist: LDAP_ALREADY_EXISTS is error code 68.
--Quanah
--
Quanah Gibson-Mount Sr. Member of Technical Staff Zimbra, Inc A Division of VMware, Inc.
Zimbra :: the leader in open source messaging and collaboration
--On Friday, July 12, 2013 10:37 PM +0530 Ashok Kumar Shah ashok.shah@flipkart.com wrote:
Is there a way to reliable determine whether ldap slave is in sync with master? Currently i am using ContextCSN diff between master and slave to determine the lag.
Well, you don't mention what version of OpenLDAP you are using, but I'd suggest using the most current release for starters if you aren't. You can read over the change logs to see the various fixes to MMR:
http://www.openldap.org/software/release/changes.html
Also, I personally prefer to use delta-syncrepl for replication. It takes less overhead, and I've found it to be quite reliable.
I use the CSNs to determine if they are in sync as well.
--Quanah
--
Quanah Gibson-Mount Sr. Member of Technical Staff Zimbra, Inc A Division of VMware, Inc. -------------------- Zimbra :: the leader in open source messaging and collaboration
openldap-technical@openldap.org
-
Ashok Kumar Shah -
Quanah Gibson-Mount