[Date Prev][Date Next]
Re: (ITS#4059) The 'nretries' parameter in back-meta configuration
This portion of back-meta (and back-ldap) is a work in progress; the code
is being changed frequently based on the results of the experimentation
we're conducting. The current setup seems to represent a robust and
reliable compromise between performances and failover on the different
platforms we're using right now. If no more changes occur, I'll take this
ITS as a reminder of lining up the man page.
> Full_Name: Ali Pouya
> Version: 2.3.7
> OS: Linux Redhat Advanced Serveur 3
> URL: ftp://ftp.openldap.org/incoming/
> Submission from: (NULL) (220.127.116.11)
> The "nretries" parameter is very useful in back-meta configurations with
> targets and targets with sophsiticated access paths.
> The man page slapd-meta says this about "nretries" :
> "This directive defines how many times a bind should be retried ...
> I have the following remarks :
> 1) This is only the number of META_BIND_TIMEOUT wait cycles. There in no
> retry". Only one BIND request is really sent to the target.
> 2) The default value is not "never" but taken from the META_RETRY_DEFAULT
> definition in back-meta.h. This value is 3 in the release 2.3.7 (I
> modified it
> for my own use).
> 3) In case of failure an ABANDON request is sent to the target. After this
> same number of wait cycles is engaged. Is it really necessary to wait so
> after an ABANDON ?
> Thanks for this useful back-end and particularly the recent evolutions.
> Best Regards
> Ali Pouya
SysNet - via Dossi,8 27100 Pavia Tel: +390382573859 Fax: +390382476497