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

(ITS#5640) slapd scans too many objects at startup

Full_Name: Ali Pouya
Version: 2.4.11
OS: Linux 2.6
URL: ftp://ftp.openldap.org/incoming/
Submission from: (NULL) (

I have a test directory with two mirrors A and B and a replica C connected to
I usaually use server A for write operations. 

I encounter the following problems :

1) If the data base is initiated in stand alone (so serverID defaults to zero)
and then I set serverIDs 1 and 2 for A and B then each time I start up slapd on
C it scans all of the objects writtent on A afterwards, producing the followin
log for each object :

entry_decode: "cn=testr1,ou=resources,ou=mefi,o=gouv,c=fr"
<= entry_decode(cn=testr1,ou=resources,ou=mefi,o=gouv,c=fr)
=> bdb_dn2id("cn=testr1,ou=resources,ou=mefi,o=gouv,c=fr")
<= bdb_dn2id: got id=0x9
=> test_filter
=> access_allowed: search access to "cn=testr1,ou=resources,ou=mefi,o=gouv,c=fr"
"entryCSN" requested
<= root access granted
=> access_allowed: search access granted by manage(=mwrscxd)
<= test_filter 6

For a directory with 10 million objects the this takes more than one hour (slapd
is running but the service is not available).
If I set  serverID=3 on the replica C the problem disapears.

2) If I do only one write operation on B, then I get two contextCSN values,
which is normal.

But il this case slapd on B scans, at each startup, all objecs written on A
after the write operation on B. 
The log and the effect are similar to those explained above.

Should I consider this as a normal behaviour or a bug ?

My mirror configuration is similar to the one recommended in Admin's Guide.
Of course I can provide more detailed information if required.

Thanks for your HELP
Best Regards