[Date Prev][Date Next]
Re: ContextCSN generation
--On Wednesday, October 10, 2012 11:07 AM -0500 Sven Jourgensen
I have an odd issue, where I have some new slaves that I added to my pool,
they ran fine sync'ing with the master, etc. for weeks, until I added them
into use (we're using an F5 frontend) whereupon they started getting a
contextCSN which was larger than that of the master.
How is the contextCSN generated, I thought the slave could never get ahead
of the master, but it's happening consistently, it's not a transient
thing, the slave gets a larger contextCSN and keeps it, until the master
is updated again.
master: contextCSN: 20121010154339.775633Z#000000#000#000000
slave1: contextCSN: 20121010154442.858054Z#000000#000#000000
slave2: contextCSN: 20121010154351.807575Z#000000#000#000000
As soon as I remove them from use, and update the master, they come back
OpenLDAP version? Configs for master and replicas? Have you verified that
the clocks on all 3 servers are in sync?
Sr. Member of Technical Staff
A Division of VMware, Inc.
Zimbra :: the leader in open source messaging and collaboration