>> Quanah Gibson-Mount <quanah(a)zimbra.com> schrieb am
28.10.2013 um 18:10 in
--On Sunday, October 27, 2013 6:08 PM +0100 Aleksander Dzierżanowski
> I'm trying to migrate small other vendor LDAP server to OpenLDAP.
> I've created test environment with 3 multimaster OpenLDAP instances -
> version 2.4.36. Below is some strange behavior of slapd while I was
> adding few hunderd of accounts from ldif file using ‚ldapadd' command
> from remote host.
> conn=1015 op=440 ADD dn=„uid=XXX,ou=People,ou=developers,o=test"
> conn=1015 op=440 RESULT tag=105 err=0 text=
> connection_input: conn=1015 deferring operation: too many executing
> conn=1015 op=441 ADD dn=„uid=YYY,ou=People,ou=developers,o=test"
> conn=1015 op=441 RESULT tag=105 err=0 text=
Considering that the message is somewhat confusing, I can think of two
1) Quantify "too many", i.e.: if there is a numeric limit, sell the user about
it. Especially useful if the limit is configurable
2) If you send an extra log message if an operation is deferred, also send one
if the operation is finally processed, revealing the extra delay
With 1) and 2) I guess the user woundn't have been confused that much.
Despite of this, I always wondered what useful information I could get from
the monitor database...
> My question is what does mean 'deferring operation' - as you can see
> result is OK (err=0) so nothing was really deferred. Database is really
> small - few hundred entries, and server is not used at all by any other
> machine. I was using rootdn user which I suppose does not have any limits
> for search/add/mod operations?
It means the operation is deferred, exactly as stated. There are any
number of scenarios that can cause operations to be deferred. There is
nothing wrong or unexpected here, and it has zero to do with limits.
Architect - Server
Zimbra :: the leader in open source messaging and collaboration