[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
Re: entryCSN is larger (later) in consumer node than in provider node
- To: openldap-technical@openldap.org
- Subject: Re: entryCSN is larger (later) in consumer node than in provider node
- From: Dieter Klünter <dieter@dkluenter.de>
- Date: Wed, 25 May 2016 10:09:22 +0200
- In-reply-to: <CAPdEfVJm7=4i4sQYTT5tOKXSo-g1qaBQWraZarxXxoH5afcqpg@mail.gmail.com>
- Organization: AVCI
- References: <CAPdEfVKcYr0VzLWQB=4mtXJ_ayLp9Qq+Y90Rh0mitFR6wi=M6w@mail.gmail.com> <F7BFA5BFA93A0DDC28C3CFDD@192.168.1.19> <CAPdEfVJry8BJnEZX86Dwe_6-AttN35ONbbr5zCs0pQFERCt=Zg@mail.gmail.com> <91D632D14CF870E93653AF84@192.168.1.19> <CAPdEfVJm7=4i4sQYTT5tOKXSo-g1qaBQWraZarxXxoH5afcqpg@mail.gmail.com>
Am Tue, 24 May 2016 15:55:04 -0400
schrieb Frank Luo <frank.luoy@gmail.com>:
> but we always have two masters - and you can tell that this is pretty
> current time tag.
>
> contextCSN: 20160521215740.310825Z#000000#000#000000
>
> Does this mean the slave gets updated from some other source in
> additional to the two masters.
This just means the update comes from a source which has not configured
a serverID.
-Dieter
--
Dieter Klünter | Systemberatung
http://sys4.de
GPG Key ID: E9ED159B
53°37'09,95"N
10°08'02,42"E