[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
Antw: Re: another CSN too old N-WAY master
Hi!
Are you sure you are chasing a real problem? AFAIK, in multi-master sync, the
server that receives a change will send that change to all other nodes, which,
in turn, will also send the changes received to all other nodes. That means
that the original submitter of the changes will receive ist own change.
I also think that "too old" means "not newer" here. I wonder if the message
shouldn't be dropped instead of complaining that the requested change is
already there.
The gurus may correct me if I'm wrong.
Regards,
Ulrich
>>> Lanfeust troy <lanfeust99@gmail.com> schrieb am 08.10.2013 um 10:13 in
Nachricht
<CAJ=nZHMkk9hd7UdcrDW6zirjheBXqcjkhHBFEbvP3nTJu+v9Fg@mail.gmail.com>:
> another logs with 2.4.36
>
> ldap-int1 receive syncrepl modification from ldap-int2 with this log:
>
> ldap-int1 log:
> syncprov_matchops: skipping original sid 002
> Oct 4 15:00:24 ldap-int1 slapd[24555]: slap_graduate_commit_csn: removing
> 0x7f7bf8200b40 20131004150021.988007Z#000000#002#000000
> Oct 4 15:00:24 ldap-int1 slapd[24555]: syncrepl_entry: rid=102 be_add
> cn=502296-xxxxxx,ou=aaaaa,ou=bbbb,o=cccc,c=dd (0)
> ... ...
>
> ldap-ext2 receive the same modification an reply to ldap-int1 with new
> cookie
>
> ldap-int1 log
> Oct 4 15:00:24 ldap-int1 slapd[24555]: do_syncrep2: rid=103 NEW_COOKIE:
>
rid=103,sid=004,csn=20130304121522.188962Z#000000#000#000000;20131004082718.
>
688747Z#000000#001#000000;20131004150023.350876Z#000000#002#000000;2013092009
>
4950.036431Z#000000#003#000000;20130930134451.718477Z#000000#004#000000;20130
> 304131428.455916Z#000000#00b#000000;20130304125618.164164Z#000000#00c#00000
>
> Another modification from ldap-int2 isn't apply to ldap-int1 because of csn
> too old
>
> Oct 4 15:00:24 ldap-int1 slapd[24555]: syncrepl_entry: rid=102 be_add
> cn=502296-bbbb,ou=aaaaa,ou=bbbb,o=cccc,c=dd (0)
> Oct 4 15:00:24 ldap-int1 slapd[24555]: do_syncrep2: rid=102
> cookie=rid=102,sid=002,csn=20131004150022.050845Z#000000#002#000000
> Oct 4 15:00:24 ldap-int1 slapd[24555]: do_syncrep2: rid=102 CSN too old,
> ignoring 20131004150022.050845Z#000000#002#000000
> (cn=502296-bbbb,ou=aaaaa,ou=bbbb,o=cccc,c=dd)
> Oct 4 15:00:24 ldap-int1 slapd[24555]: do_syncrep2: rid=102
> cookie=rid=102,sid=002,csn=20131004150022.100121Z#000000#002#000000
>
>
>
>
>
> 2013/10/4 Lanfeust troy <lanfeust99@gmail.com>
>
>> No; it's not the problem
>>
>>
>> 2013/10/4 Michael StrÃder <michael@stroeder.com>
>>
>>> On Fri, 4 Oct 2013 11:05:57 +0200 Lanfeust troy <lanfeust99@gmail.com>
>>> wrote
>>> >
>>> > I have upgraded to 2.4.36 openLDAP version. The problem still exists.
>>> > It seem to be appear less than before. This week this problem occur
only
>>> > once.
>>>
>>> I did not follow your issue in detail.
>>> Are you using slapo-memberof in your deployment?
>>>
>>> Ciao, Michael.
>>>
>>>
>>>
>>