[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: retry= syncrepl directive

I confirmed your analysis of "retry" with good old tcpdump. Here is what I got from analyzing the code.

1.  "retry" accepts a comma separated list of number pairs
    (+ may be used in the second value of a pair).
2.  The first value of the pair is the "retry interval" in seconds
3.  The second value of the pair is the "number of retries"
   "+" or "-1" may be used for an infinite number of retries

Ex.  retry=1,2,3,4,5,+ means
   retry 2 times every 1 second then
   retry 4 times every 3 seconds then
   retry every 5 seconds indefinately

I'll post this in the FAQ-O-Matic

Cheers, James.

To follow up on my own post, I have tried:

	retry=5,5,300,+

which appears to work. From reading the code, I think this means
"retry five times every five seconds, then retry every five minutes
perpetually". But I would appreciate some confirmation from someone
that actually understands this code :-)

-- Luke

From: Luke Howard <lukeh@PADL.COM>
Subject: retry= syncrepl directive
To: openldap-software@OpenLDAP.org
Date: Wed, 18 Aug 2004 14:30:41 +1000
Organization: PADL Software Pty Ltd
Versions: dmail (bsd44) 2.6d/makemail 2.10


Whilst testing 2.2.15 I notice that syncrepl has regressed, in that
ITS #3032 has reappeared.

Reading through the code suggest that the "retry=" syncrepl directive
has been added, which may with suitable configuration ameliorate this
problem, but I cannot find any documentation of this change in behaviour,
which appears to be non-obvious.

Can anyone help?

-- Luke