Dears,
In context of a 4 MMR mirrored, if I do a ldapsearch for contextCSN of cn=config, I get following output :
contextCSN: 20210720121843.555301Z#000000#000#000000 contextCSN: 20211001095511.729248Z#000000#001#000000 contextCSN: 20211021090559.554997Z#000000#002#000000 contextCSN: 20211025120556.001311Z#000000#003#000000 contextCSN: 20211021090202.909879Z#000000#004#000000
which is correct as I've 4 servers, but if I do same request for my own dn DB o=xxxx.be, I get following output :
contextCSN: 20211116155042.534901Z#000000#001#000000 contextCSN: 20211116153150.449895Z#000000#002#000000
for me I should receive 003 & 004 ones too as they are in mirrored mode, no ?
Can you advice ?
Thx, Jean-Luc.
On 11/16/21 19:09, bourguijl@gmail.com wrote:
but if I do same request for my own dn DB o=xxxx.be, I get following output :
contextCSN: 20211116155042.534901Z#000000#001#000000 contextCSN: 20211116153150.449895Z#000000#002#000000
for me I should receive 003 & 004 ones too as they are in mirrored mode, no ?
Basically the contextCSN is the highest entryCSN generated by a numbered replica.
So if you never sent a write operation to replica 003 & 004 they did not generate an entryCSN yet.
Ciao, Michael.
--On Tuesday, November 16, 2021 8:00 PM +0100 Michael Ströder michael@stroeder.com wrote:
On 11/16/21 19:09, bourguijl@gmail.com wrote:
but if I do same request for my own dn DB o=xxxx.be, I get following output :
contextCSN: 20211116155042.534901Z#000000#001#000000 contextCSN: 20211116153150.449895Z#000000#002#000000
for me I should receive 003 & 004 ones too as they are in mirrored mode, no ?
Basically the contextCSN is the highest entryCSN generated by a numbered replica.
So if you never sent a write operation to replica 003 & 004 they did not generate an entryCSN yet.
Correct, except "provider" not "replica".
--Quanah
--
Quanah Gibson-Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: http://www.symas.com
openldap-technical@openldap.org