[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
Syncrepl out-of-sync detection.
- To: OpenLDAP-software@OpenLDAP.org
- Subject: Syncrepl out-of-sync detection.
- From: "Jose Ildefonso Camargo Tolosa" <ildefonso.camargo@gmail.com>
- Date: Mon, 21 Aug 2006 22:08:52 -0400
- Content-disposition: inline
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=f0TniDiOus37JQqd440BXyfQ5f145bazTV2IBWJfQOWeckBzeQ34eztck6jHToxTQqFc0CLZrjs5bonpPEFoKAqHmtokMXk44PoqAnqvVxmcJIDcDaC2jA1CS0x2VdjxmGIfOtLCwl/TxHqGcBONzHBPfr9BnwDA8Eomlkv8/CE=
Hi!
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.
Thanks in advance,
Ildefonso Camargo.