[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: Two contextCSNs

Peter Mogensen wrote:
I'm trying to understand why changes made to SID 1 in my mirror set
while SID 2 is down does not get propagated to SID 2 when it comes up.

You've posted quite a lot of stuff on that topic already, but nothing useful that could help anyone else to see what you're actually doing. (E.g., such essentials as your software version, config files, and the actual commands/operations you perform in the precise sequence you execute them.)

I did another test, resulting in SID 2 having two contextCSNs:

root object:
entryCSN: 20091204151327.370998Z#000000#001#000000
contextCSN: 20091204151327.735435Z#000000#001#000000
contextCSN: 20091204151430.680725Z#000000#002#000000

However, no changes has been made to server2.
Only to server1.

No entry has the CSN with sid=002.

Is this expected?

It is not entirely unexpected...

If the last operation that occurred on that server was a Delete, then the contextCSN will be the CSN of that Delete operation, but obviously there will not be any entry in the server with that CSN.

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