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

Re: (ITS#5825) syncrepl default is no retry

hyc@symas.com wrote:
> ando@sys-net.it wrote:
>> Full_Name: Pierangelo Masarati
>> Version: irrelevant
>> OS: irrelevant
>> URL: ftp://ftp.openldap.org/incoming/
>> Submission from: (NULL) (
>> Submitted by: ando
>> Syncrepl by default uses no retry.  This is extremely useless, as syncrepl with
>> no retry will probably break, sooner or later, without notifying why it
>> happened.
> Legacy behavior, since retry was added later...
>> I believe it would be safe to have either:
>> - a "safe" retry value (not too often, e.g. every hour, forever)
> Sounds fine, just add it to the doc.
>> - a warning (or an error) if retry is not given when configuring syncrepl
> Sounds rather annoying. We could combine these: if no retry was configured, 
> give the warning and use a default of 1 hour. Have to ensure that the default 
> setting doesn't persist in cn=config, so that it will keep warning until an 
> explicit value is set.
>> Another interesting feature would be to register syncrepl-specific parameters in
>> back-monitor's entry of each database, that
>> - show the status of syncrepl (whether it's up, if rp)
>> - show the timestamp of the last successful refresh
>> - show the timestamp of the last failed attempt, and the reason of the failure
> Sounds fine, but unless you can add these quickly I don't see any reason to 
> hold 2.4.13 for it.

Didn't mean to :)  By now, only the warning is being issued.  I don't 
think I can implement the rest for 2.4.13, will need to wait for next 


Ing. Pierangelo Masarati
OpenLDAP Core Team

SysNet s.r.l.
via Dossi, 8 - 27100 Pavia - ITALIA
Office:  +39 02 23998309
Mobile:  +39 333 4963172
Fax:     +39 0382 476497
Email:   ando@sys-net.it