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

Re: High CPU usage with syncrepl on 2.26

To: openldap <openldap-software@OpenLDAP.org>
Subject: Re: High CPU usage with syncrepl on 2.26
From: Ben Beuchler <insyte@gmail.com>
Date: Wed, 9 Nov 2005 09:07:53 -0600
Content-disposition: inline
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=S5Xskqj05kqKdpQ3/fHsv8Hy3lzJSttTawUCbVq6BYguAcdPCNLZF+AejEDpRnfTDthz5zLOP/n0gtJe/LFHR2Im4x8fV4j87hq4fofrUS6G33XQGMBvCzYx1bCdUsV+MZ4H0XIKLmBNoJdzPIZ6B6QMt3g3ozKNGIAYr2DywCU=
In-reply-to: <200511090834.27345.bgmilne@staff.telkomsa.net>
References: <479b70ed0511080943q704da4beu43551eb4b2ef0779@mail.gmail.com> <200511090834.27345.bgmilne@staff.telkomsa.net>

> There is no updatedn option for sycnrepl ....

It's listed in both slapd.conf(5) and in the OpenLDAP admin doc...

> > Any thoughts on why this might be happening?
>
> Are you indexing the entryCSN and entryUUID attributes?

I'm indexing  entryUUID, but I haven't been indexing entryCSN.  I'll
add that and see what happens.

I am going to switch to 2.3.x ASAP, though.

-Ben

Follow-Ups:
- Re: High CPU usage with syncrepl on 2.26
  - From: Quanah Gibson-Mount <quanah@stanford.edu>

References:
- High CPU usage with syncrepl on 2.26
  - From: Ben Beuchler <insyte@gmail.com>
- Re: High CPU usage with syncrepl on 2.26
  - From: Buchan Milne <bgmilne@staff.telkomsa.net>

Prev by Date: Re: Pb with my BDB: openldap don't start
Next by Date: replication security
Index(es):
- Chronological
- Thread