[Date Prev][Date Next]
Re: (ITS#5825) syncrepl default is no retry
> Full_Name: Pierangelo Masarati
> Version: irrelevant
> OS: irrelevant
> URL: ftp://ftp.openldap.org/incoming/
> Submission from: (NULL) (220.127.116.11)
> 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
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.
-- Howard Chu
CTO, Symas Corp. http://www.symas.com
Director, Highland Sun http://highlandsun.com/hyc/
Chief Architect, OpenLDAP http://www.openldap.org/project/