[Date Prev][Date Next]
Re: Index for objectclass does not work...
- To: Bjørn Ruberg <firstname.lastname@example.org>
- Subject: Re: Index for objectclass does not work...
- From: Steeg Carson <email@example.com>
- Date: Mon, 3 Jan 2011 21:22:25 +0100
- Cc: firstname.lastname@example.org
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=/+wL4ZhpdKe+Wy1CGEbdweIwRE0S5sKmDN43Gjy64fM=; b=dM2GEbYISzLH63DD44jmRDcRkFOjM3a7TuIT+LR75/VpSCCsk4lgCpr6tpiMweSOyH bFcuIb4Uz3r5eqU7W8cic/XVr2y5Bm7yJdfFc9XjpwEcCCbzWgU/WYcC/YoQoK0PD/x1 SibqFhipSB3c8aPfR1rLzAjJ7AXVYFtIDSYwA=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=iNno+504/SdBSgvfqHP172lG+HMgdJrkvuSPx2zkQ6XmPSAYS37yIon+3pJK11Dubw cgE78S7Z3GuBszcjhMzC0Q8W9zv/70Ai+uNaPuES5RNybn4LePQKwQVKC/KNmTUXlnnW pxkbyP6GhtCm9xt3WMSa3LyMo72hUNCiYt2Xo=
- In-reply-to: <4D2211D2.email@example.com>
- References: <AANLkTikgxiznuoh_i=BP_Tegj6scCHSp5tv0xfgxKX07@mail.gmail.com> <4D2211D2.firstname.lastname@example.org>
>> PS: During the first search, the disk is heavy used (iotop) by writing
>> from slapd.conf ... why it - should only read ...?
> This does not make sense. slapd should not *write* to slapd.conf.
Soryy, the correct sentence is: "During the first search, the disk is
heavy used (seen with iotop) by writing from slapd, why - it should
only read ...?"
I apologizes for this mistake!
> You should probably learn how to use strace to find out what really happens
> on your system.
I also used strace to catch the problem, but i did not find where the
slapd write to disk. It seems, it comes via set up the futex write
locks? I'm not a kernel programmer and the code from openldap is hard
to read. But strace I use for several years to find errors, it was
also the first choice for me, to find the error. It is not a normal
file that will be written...
This behavior can be reproduce:
=> Large Database (eg. 500.000 objects/DN's)
=> put the one (same) Objectclass to >100.000 objects/DNs
=> turn of logging
=> start iotop (+ hit "o")
=> search for this objectclass and look what will happen during the
first search with your disk
> You should also install the same LDAP database and the same
> config on another physical server to see whether it behaves equally there.
I checked this problem on several machines, openldap versions (2.4.11,
2.4.21, 2.4.23) and Distribution (Debian 5, and Opensuse 11.1 and
I investigated a lot time till now to find the error, but nothing helped ...
> Good luck with your troubleshooting,