[Date Prev][Date Next]
Re: LDAP Writes are not propagated to mirror nodes.
- To: Gavin Henry <email@example.com>
- Subject: Re: LDAP Writes are not propagated to mirror nodes.
- From: Howard Chu <firstname.lastname@example.org>
- Date: Wed, 12 Mar 2008 18:53:49 -0700
- Cc: "K C, Sachin \(Sachin\)" <email@example.com>, firstname.lastname@example.org
- In-reply-to: <47C5FB84.email@example.com>
- References: <439883738F3074439FE043280078D231012D2966@SGEXC1U01.AP.LUCENT.COM> <47C5FB84.firstname.lastname@example.org>
- User-agent: Mozilla/5.0 (X11; U; Linux i686; rv:1.9b5pre) Gecko/2008030700 SeaMonkey/2.0a1pre
Gavin Henry wrote:
K C, Sachin (Sachin) wrote:
Find in the attached the config files for 2 nodes (node1.conf
initial.ldif file contains the LDIF data.
Well I've spent 3 hours tonight testing various settings and operations;
It seems very inconsistent. For example, I'll add 5 new users on node2
and node1 will only add one of them and stop at:
bdb_modify_internal: 0x00000001: o=ORG
bdb_modify: modify failed (16)
send_ldap_result: conn=-1 op=0 p=0
null_callback : error code 0x10
syncrepl_updateCookie: rid=001 be_modify failed (16)
I took a look at this just now. This is a (stupid) interaction between
syncrepl and syncprov's checkpoint; syncprov has already updated the
contextCSN so when syncrepl tries to delete the old value it fails because
syncprov has already deleted it.
The simple workaround for now is to just turn off the syncprov-checkpoint.
It's unnecessary in the mirror/multimaster config since syncrepl will always
keep the contextCSN up to date itself.
-- Howard Chu
Chief Architect, Symas Corp. http://www.symas.com
Director, Highland Sun http://highlandsun.com/hyc/
Chief Architect, OpenLDAP http://www.openldap.org/project/