From 7e454e074a46c43458a198d3ff37b80d1040c95c Mon Sep 17 00:00:00 2001 From: Jong Hyuk Choi Date: Wed, 27 Oct 2004 18:29:01 +0000 Subject: [PATCH] syncrepl retry parameter --- doc/guide/admin/slapdconfig.sdf | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/doc/guide/admin/slapdconfig.sdf b/doc/guide/admin/slapdconfig.sdf index 7d1a6c1a3f..27316af998 100644 --- a/doc/guide/admin/slapdconfig.sdf +++ b/doc/guide/admin/slapdconfig.sdf @@ -421,6 +421,7 @@ H4: syncrepl > provider=ldap[s]://[:port] > [type=refreshOnly|refreshAndPersist] > [interval=dd:hh:mm:ss] +> [retry=[ <# of retries>]+] > [searchbase=] > [filter=] > [scope=sub|one|base] @@ -490,6 +491,13 @@ remains persistent in the provider slapd. Further updates to the master replica will generate {{EX:searchResultEntry}} to the consumer slapd as the search responses to the persistent synchronization search. +If an error occurs during replication, the consumer will attempt to reconnect +according to the retry parameter which is a list of the +and <# of retries> pairs. For example, retry="60 5 300 3" lets the consumer +retry every 60 seconds for the first 10 times and then retry every 300 seconds +for the next three times before stop retrying. + in <# of retries> means +indefinite number of retries until success. + The schema checking can be enforced at the LDAP Sync consumer site by turning on the {{EX:schemachecking}} parameter. If it is turned on, every replicated entry will be checked for its -- 2.39.5