[Date Prev][Date Next]
Re: Syncrepl out-of-sync detection.
Quanah Gibson-Mount wrote:
The fast yes/no answer is simply to compare the contextCSNs, as Quanah
noted. If you want to know which entries are not yet sync'd, you can do
essentially what the syncrepl engine does, and search for entries on the
provider with entryCSN >= the contextCSN of the consumer. Of course, in
the amount of time it takes to do that, the consumer would be able to
sync itself already...
--On Monday, August 21, 2006 10:08 PM -0400 Jose Ildefonso Camargo
Tolosa <firstname.lastname@example.org> wrote:
I know that this question may have been asked before on this forum.
But I just can't find the threads where it was discussed.
Is there a way of telling wich slaves are not on sync on a syncrepl
deployment? I mean, a "fast" way of telling whether "this" replica is
not in sync.
Examine the contextCSN value of the DIT being replicated?
-- Howard Chu
Chief Architect, Symas Corp. http://www.symas.com
Director, Highland Sun http://highlandsun.com/hyc
OpenLDAP Core Team http://www.openldap.org/project/