Re: (ITS#8432) Never ending operation modifications with 3+ MMR nodes

[quanah@zimbra.com]

--On Thursday, June 09, 2016 1:19 AM +0100 Howard Chu <hyc@symas.com> wrote:

> quanah@openldap.org wrote:
>> Full_Name: Quanah Gibson-Mount
>> Version: 2.4.44
>> OS: Linux 2.6
>> URL: ftp://ftp.openldap.org/incoming/
>> Submission from: (NULL) (75.111.52.177)
>>
>>
>> In MMR node, when there is > 2 nodes, operations can get sent out
>> endlessly.
>>
>> For example, we see this modification occur at 20160603194926.427963Z
>
> You seem to have a large clock sync problem.
>>
>> Jun  3 14:49:22 ldap01 slapd[14014]: syncrepl_message_to_op: rid=100
>> be_modify cn=edge02e.zimbra.com,cn=servers,cn=zimbra (0)
>> Jun  3 14:49:22 ldap01 slapd[14014]: syncprov_sendresp: to=002,
>> cookie=rid=100,sid=003
>> Jun  3 14:49:22 ldap01 slapd[14014]: slap_queue_csn: queueing 0x121c8680
>> 20160603194926.417898Z#000000#001#000000
>> Jun  3 14:49:22 ldap01 slapd[14014]: slap_graduate_commit_csn: removing
>> 0x9403600 20160527111854.508810Z#000000#004#000000
>
> How did a CSN from 20160527 get queued on 20160603?

Because it had been going around non-stop since 5/27 (5/27 is when I did 
the modification).

--Quanah

--

Quanah Gibson-Mount
Platform Architect
Manager, Systems Team
Zimbra, Inc.
--------------------
Zimbra ::  the leader in open source messaging and collaboration
A division of Synacor, Inc