Re: (ITS#7710) contextCSN values not updated by internal non-replicated ops

[hyc@symas.com]

Howard Chu wrote:
> Michael Ströder wrote:
>> On Wed, 09 Oct 2013 05:01:40 -0700 Howard Chu <hyc@symas.com> wrote
>>
>>> michael@stroeder.com wrote:
>>>> I've updated the test data with LDIF files and a README describing the LDAP
>>>> operations to perform:
>>>>
>>>> http://www.stroeder.com/temp/openldap-testbed-its7710.tar.bz2
>>>>
>>>> I consider this to be a serious issue which could be the cause for other
>>>> replication issues including dead-locks we're experiencing. (Maybe there
>>>> are similar issues in slapo-refint since dead-locks in our deployment
>>>> arised when moving entries into different subtree.)
>>>
>>> Thanks, fixed now in master. Looks like refint may have run into the same
>>> issue, also patched in master.
>>
>> contextCSN values are correct now.
>>
>> But now I see this during initial refresh phase of second server:
>>
>> send_ldap_result: err=20 matched="" text="modify/add: memberOf: value #0
>> already exists"
>>
>> Is that expected?
>
> Not seeing that with your testcase.
>
Ah, I see it now. Yes, it's normal; memberOf on the provider already added the 
relevant values. The consumer receives a group entry and performs the same set 
of memberof updates, which are redundant at that point. It's harmless.

-- 
   -- Howard Chu
   CTO, Symas Corp.           http://www.symas.com
   Director, Highland Sun     http://highlandsun.com/hyc/
   Chief Architect, OpenLDAP  http://www.openldap.org/project/