Hariharan R wrote:
The supplier will automatically update the consumer when it contacts the consumer. The supplier attempts to contact the consumer periodically. It uses a backoff strategy that has a maximum time of 5 minutes. So at most, the consumer will be about 5 minutes behind the supplier.Hi, Thanks for your reply.Let us take the scenario in which the consumer server is taken off line for maintenance purpose. When the consumer server comes back online, how does it initialize (update) it's replica? Because in the mean time supplier server may have been updated.
It doesn't. There is no way for the consumer to contact the supplier directly. If 5 minutes is too long, there is a way for an operator to force sending updates. You can do this using ldapmodify - modify the replication schedule in the replication agreement entry to "close the window" e.g. use something like 0000-0001 0 (i.e. replicate between midnight and 12:01 Sunday morning). Then, immediately change the schedule back to what it was (usually 0000-2359 * or "* *"). This will have the effect of forcing the supplier to send all of its updates immediately.If only supplier initiated replication is supported by Fedora Directory Server, how does the supplier know that the consumer has come back online ?
Regards, Hariharan RHi,Does the Fedora Directory Server support consumer initiated replication. If not, is there any work around for this ?No Fedora DS does not support consumer initiated replication. For what reasons do you require CIR?Please advise.--- Hariharan.R -- Fedora-directory-users mailing list Fedora-directory-users@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-directory-users
Attachment:
smime.p7s
Description: S/MIME Cryptographic Signature
-- Fedora-directory-users mailing list Fedora-directory-users@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-directory-users
