[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
Antwort: Re: (ITS#4758) valsort + dynlist can cause 100% cpu utilization causing slapd to become unresponsive
Dies ist eine mehrteilige Nachricht im MIME-Format.
--=_alternative 005BCC39C1257261_=
Content-Type: text/plain; charset="US-ASCII"
Today I deployed a patched 2.3.32 version on one of our replicas and
changed the config to include the aforementioned dynlist/valsort
construct.
It's been running nicely for a few hours now. Seems like the patch fixed
this issue. Thank you very much!
With kind regards
Michael Heep
Pierangelo Masarati <ando@sys-net.it>
11.01.2007 23:37
An
michael.heep@o2.com
Kopie
openldap-its@openldap.org
Thema
Re: (ITS#4758) valsort + dynlist can cause 100% cpu utilization causing
slapd to become unresponsive
michael.heep@o2.com wrote:
> the following valsort + dynlist combination causes slapd to utilize 100%
cpu
> time when issueing searches against parts of the DIT containing
attribute-value
> pairs "created" by dynlist:
>
> overlay dynlist
> dynlist-attrset extensibleObject memberURL uniqueMember
>
> overlay valsort
> valsort-attr uniqueMember dc=o2online,dc=de alpha-ascend
>
> When run independent both overlays work flawlessly.
>
A bug (ITS#4801) was recently fixed in slapo-dynlist(5) which appeared
in conjunction with slapo-valsort(5). The fix is available both in HEAD
and in re23 CVS (tag OPENLDAP_REL_ENG_2_3). The relevant change is in
servers/slapd/overlays/dynlist.c 1.28 -> 1.29 (HEAD) or 1.5.2.9 ->
1.5.2.10 (re23). Could you please check if it does any good to the
issue you reported?
Thanks, p.
Ing. Pierangelo Masarati
OpenLDAP Core Team
SysNet s.n.c.
Via Dossi, 8 - 27100 Pavia - ITALIA
http://www.sys-net.it
------------------------------------------
Office: +39.02.23998309
Mobile: +39.333.4963172
Email: pierangelo.masarati@sys-net.it
------------------------------------------
--=_alternative 005BCC39C1257261_=
Content-Type: text/html; charset="US-ASCII"
<br><font size=2 face="sans-serif">Today I deployed a patched 2.3.32 version
on one of our replicas and changed the config to include the aforementioned
dynlist/valsort construct.</font>
<br><font size=2 face="sans-serif">It's been running nicely for a few hours
now. Seems like the patch fixed this issue. Thank you very much!</font>
<br>
<br><font size=2 face="sans-serif">With kind regards</font>
<br><font size=2 face="sans-serif">Michael Heep<br>
</font>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td width=40%><font size=1 face="sans-serif"><b>Pierangelo Masarati <ando@sys-net.it></b>
</font>
<p><font size=1 face="sans-serif">11.01.2007 23:37</font>
<td width=59%>
<table width=100%>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">An</font></div>
<td><font size=1 face="sans-serif">michael.heep@o2.com</font>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">Kopie</font></div>
<td><font size=1 face="sans-serif">openldap-its@openldap.org</font>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">Thema</font></div>
<td><font size=1 face="sans-serif">Re: (ITS#4758) valsort + dynlist can
cause 100% cpu utilization causing slapd to become unresponsive</font><font size=2 face="sans-serif">
</font></table>
<br>
<table>
<tr valign=top>
<td>
<td></table>
<br></table>
<br>
<br>
<br><font size=2><tt>michael.heep@o2.com wrote:<br>
> the following valsort + dynlist combination causes slapd to utilize
100% cpu<br>
> time when issueing searches against parts of the DIT containing attribute-value<br>
> pairs "created" by dynlist:<br>
><br>
> overlay dynlist <br>
> dynlist-attrset extensibleObject
memberURL uniqueMember <br>
><br>
> overlay valsort <br>
> valsort-attr uniqueMember dc=o2online,dc=de alpha-ascend<br>
><br>
> When run independent both overlays work flawlessly.<br>
> <br>
A bug (ITS#4801) was recently fixed in slapo-dynlist(5) which appeared
<br>
in conjunction with slapo-valsort(5). The fix is available both in
HEAD <br>
and in re23 CVS (tag OPENLDAP_REL_ENG_2_3). The relevant change is
in <br>
servers/slapd/overlays/dynlist.c 1.28 -> 1.29 (HEAD) or 1.5.2.9 ->
<br>
1.5.2.10 (re23). Could you please check if it does any good to the
<br>
issue you reported?<br>
<br>
Thanks, p.<br>
<br>
<br>
<br>
Ing. Pierangelo Masarati<br>
OpenLDAP Core Team<br>
<br>
SysNet s.n.c.<br>
Via Dossi, 8 - 27100 Pavia - ITALIA<br>
http://www.sys-net.it<br>
------------------------------------------<br>
Office: +39.02.23998309<br>
Mobile: +39.333.4963172<br>
Email: pierangelo.masarati@sys-net.it<br>
------------------------------------------<br>
<br>
</tt></font>
<br>
--=_alternative 005BCC39C1257261_=--